Thanks a lot
On Thursday, February 14, 2019 at 11:33:17 PM UTC+2, Tom Duerr wrote:
>
> Hi,
> We use a when clause to run the stage or not based on finding
> a specific string in the commit message
>
> stage('Publish') {
> // if we dont find SKIP_PUBLISH in git log
> // then we proceed wit
Hi,
We use a when clause to run the stage or not based on finding
a specific string in the commit message
stage('Publish') {
// if we dont find SKIP_PUBLISH in git log
// then we proceed with push
// note, we're checking the status of the grep command
// not the output. grep status
>
> Thanks on the tip
>
> Can you please elaborate how did you exit ?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroup
Hi,
It's not the cleanest approach but we get around a similar issue by adding
a specific string into the commit message( like "No Build")
then in the Jenkinsfile we look for that string and exit if we find it.
Tom
On Tue, Feb 12, 2019 at 7:24 AM Steven Foster
wrote:
> I'm not sure what's avai
I'm not sure what's available for Gitlab, but some other SCMs have a plugin
that allows commits by certain authors be skipped/ignored.
https://github.com/jenkinsci/scm-trait-commit-skip-plugin for example.
If there is no such plugin for Gitlab, it might be easy enough to make one
or contribute a
Hi,
I am using Multibranch Job.
I have a Webhook for my repository in gilab which is triggered when there
is a push to dev branch and then webhook starts the build in Jenkins
At the end of build process, I created and updated chaneglog file and push
it to dev branch again which would trigge
