-
Notifications
You must be signed in to change notification settings - Fork 8
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
Employ Jenkins pipeline #1167
Comments
Add simple Jenkins pipeline without deploy stage Signed-off-by: Alexander Fedorov <[email protected]>
The Jenkins pipeline in the repo can also be used to deploy (and sign) a snapshot on each push to the master branch, for example we do this in m2e: Of course the jar- and pgp-signing has to be done in that pipeline too. But having the pipeline in the repo makes it simpler to understand than a configuration in Jenkins freestyle/pipeline jobs. |
Do you suggest to add deploy stage to https://github.com/eclipse-passage/passage/blob/master/Jenkinsfile ? |
Yes. For m2e we deploy a snapshot after each master build so one can try out a change about 20min after it has been merged. If you are interested I can provide a PR to enhance the Jenkins pipeline and implement this. |
Now it is working, see https://ci.eclipse.org/passage/job/Eclipse%20Passage/job/passage/ |
Using GitHub Actions for build does not allow to check steps that requires EF infra like signing
Let's try to employ Jenkins pipeline on EF side
The text was updated successfully, but these errors were encountered: