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

RT_TRIGGER_URL causes failure in pipeline if build triggered manually #379

Open
stewcee opened this issue Feb 20, 2024 · 0 comments
Open

Comments

@stewcee
Copy link

stewcee commented Feb 20, 2024

We've added the Artifactory trigger configuration to our Jenkinsfile and it is working as expected when triggered by a change in Artifactory

We followed this example:
https://github.com/jfrog/project-examples/blob/master/jenkins-examples/pipeline-examples/declarative-examples/build-trigger-example/Jenkinsfile

The comments above RT_TRIGGER_URL mention that the value may be empty if the build isn't triggered by a change in Artifactory, however if a user tries to manually trigger this pipeline job, we get the following error:
Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: f8fe75f7-d762-4b5a-999c-b25b1da78862 java.lang.IllegalArgumentException: One or more variables have some issues with their values: RT_TRIGGER_URL

Is there a way to ignore RT_TRIGGER_URL being empty if the build is triggered manually instead of by the Artifactory trigger?

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

No branches or pull requests

1 participant