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

Jenkinsfile: Rewrite from scratch. #485

Conversation

UlrichEckhardt
Copy link
Contributor

In relation to #425 or, rather, the change in direction to use ci.travis.io infrastructure instead of GitHub Actions. Since the Jenkinsfile seems to have been unused for quite some time (last commit 2017), I thought one approach was to start from scratch to get it working first and then see which parts can be salvaged. Also, jenkins-infra/helpdesk#2776 comments indicate that the current file is not applicable to the target service.

  • 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

@timja
Copy link
Member

timja commented Feb 10, 2022

Non maintainers can't really make CI changes here without testing in a local setup as their changes to the CI configuration will be ignored for security

@UlrichEckhardt
Copy link
Contributor Author

Yes, whatever change I made wasn't picked up, so I can't help here. Maybe the approach of rewriting from scratch is a useful approach though.

@nre-ableton
Copy link
Contributor

Thanks for the effort nonetheless @UlrichEckhardt!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants