Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-73963] Extract event handlers in CvsTagAction/tagForm.jelly #105

Merged
merged 8 commits into from
Oct 22, 2024

Conversation

shlomomdahan
Copy link
Contributor

@shlomomdahan shlomomdahan commented Oct 21, 2024

JENKINS-73963

Testing done

status quo
CSP report only & restrictive

Instructions for Creating a CVS Local Repo and Jenkins Freestyle Project

Step 1: Set Up a Local CVS Repository

  1. Install CVS (if not already installed):

    • macOS: brew install cvs
    • Ubuntu/Debian: sudo apt-get install cvs
  2. Create a CVS repository:

    mkdir ~/cvs-test-repo
    cvs -d ~/cvs-test-repo init
  3. Import a project into CVS:

    mkdir ~/cvs-test-project
    cd ~/cvs-test-project
    echo "Hello, CVS!" > hello.txt
    cvs -d ~/cvs-test-repo import -m "Initial import" myproject myproject start
  4. Check out the project (optional):

    mkdir ~/cvs-working-dir
    cd ~/cvs-working-dir
    cvs -d ~/cvs-test-repo checkout myproject

Step 2: Configure Jenkins Freestyle Project

  1. Create a new Freestyle project in Jenkins.

  2. Source Code Management:

    • Select CVS.
    • Set CVSROOT: /Users/your-username/cvs-test-repo.
    • Set Remote Name: myproject.
  3. Build Step:

    • Add a Build Step: Execute Shell.
    • Use the following shell script:
    # Navigate to the directory where the project is checked out
    cd ${WORKSPACE}/myproject
    
    # List files and run a sample build command
    echo "Files in CVS project:"
    ls -la
    
    echo "Running a sample build process..."
  4. Save the Configuration.

Step 3: Build the Project

  1. Build Now: Trigger a build from Jenkins.
  2. View Console Output: Check the output to ensure the checkout and shell script executed successfully.

Submitter checklist

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests - that demonstrates feature works or fixes the issue

@basil basil added the internal label Oct 22, 2024
Copy link
Member

@basil basil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

@basil basil merged commit d2deb0a into jenkinsci:master Oct 22, 2024
1 of 3 checks passed
@basil basil changed the title [JENKINS 73963] Extract event handlers in CvsTagAction/tagForm.jelly [JENKINS-73963] Extract event handlers in CvsTagAction/tagForm.jelly Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants