[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Kevin Burnett commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes i got the dependent plugin from https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/cloudbees-bitbucket-branch-source/2.2.13-rc440.a1f1e6c1d925/, tested it out with Jason Lantz, and it works as designed. in our context, the fact that the branch is tagged excluded and therefore deleted by the orphaned item strategy (exactly as Javier Delgado said it would be) actually is a dealbreaker. we are very excited about this feature, but i think we need to wait for JENKINS-45502 to be implemented so that "ci skip" can be implemented without this side effect (FYI, Stephen Connolly / James Dumay). two additional notes: you need to specify "ci skip" without the hyphen when you specify behaviours, there are now two called "Commit message filtering behaviour" (one for pull requests and one for branches). they should probably have different names. see screenshot below. thanks a ton, Javier Delgado. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Kevin Burnett updated an issue Jenkins / JENKINS-47643 Allow [ci skip] to work for non-pull request changes Change By: Kevin Burnett Attachment: duplicate-name-in-config.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Kevin Burnett updated an issue Jenkins / JENKINS-47643 Allow [ci skip] to work for non-pull request changes Change By: Kevin Burnett Attachment: cannot-load.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Kevin Burnett commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes you are a hero. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28907) option to treat merge commiters as regular commiters
Title: Message Title Kevin Burnett commented on JENKINS-28907 Re: option to treat merge commiters as regular commiters we investigated this a bit. we found that the only difference between these two, for our repos, was that the git log included some extra commits due to it defaulting to "rev.always_show_header = 1". git whatchanged --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" git log --raw --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" there is a check in the git source code where it doesn't set rev.always_show_header to true when --diff-filter is used. so if we set diff filter to not actually filter (by including everything), the git whatchanged and git log commands return identical output for us. so the final equivalent git log command is this: git log --diff-filter=ACDMRTUXB --raw --no-merges --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" so, to include merge commits, we can simply remove the --no-merges from the git log, leaving us with: git log --diff-filter=ACDMRTUXB --raw --format="commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b" pull request at https://github.com/jenkinsci/git-client-plugin/pull/237 that uses this approach and adds merge commits! Add Comment
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Kevin Burnett commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders We only had issues with links to blue ocean pages. I can suggest the blue ocean 404 page as a possible place to put a link to the docs. I found myself on that page, weeping softly, many times. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Kevin Burnett commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders we suffered with this for a decent while, so hopefully this helps someone. we were having this issue only when running jenkins behind apache and resolved it by adding/updating these two apache config directives: AllowEncodedSlashes NoDecode ProxyPass / http://localhost:8080/ nocanon # we had been missing the "nocanon" modifier basically, follow this meticulously: https://wiki.jenkins-ci.org/display/JENKINS/Running+Jenkins+behind+Apache Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35662) Show Executor status
Title: Message Title Kevin Burnett commented on JENKINS-35662 Re: Show Executor status This is one of the features I most miss from bamboo. Here is a screenshot from an old version of bamboo: https://confluence.atlassian.com/display/BAMBOO033/Viewing+Bamboo's+Current+Activity Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41863) Folder computation / branch indexing can unexpectedly delete things when bitbucket goes down
Title: Message Title Kevin Burnett resolved as Duplicate found JENKINS-36029, which looks close enough. sorry! Jenkins / JENKINS-41863 Folder computation / branch indexing can unexpectedly delete things when bitbucket goes down Change By: Kevin Burnett Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-41863) Folder computation / branch indexing can unexpectedly delete things when bitbucket goes down
Title: Message Title Kevin Burnett created an issue Jenkins / JENKINS-41863 Folder computation / branch indexing can unexpectedly delete things when bitbucket goes down Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2017/Feb/08 9:21 PM Environment: Jenkins ver. 2.40 Bitbucket Branch Source Plugin 2.0.2 Atlassian Bitbucket (server) v4.6.0 Labels: git plugin scm bitbucket pipeline Priority: Major Reporter: Kevin Burnett We use bitbucket server (former known as stash) to internally host a bunch of repos. We have a number of "Bitbucket Team/Project" items set up. These map one to one with bitbucket server projects, and each one scans all of the repos (and their branches), looking for Jenkinsfiles and creating subitems for each repo (and branch). It also deletes branches (and I assume repos) when the branches and repos go away. This is all pretty sweet. Then our Bitbucket Server "went down" (the JVM locked up) and we kicked it to get it fired back up. We found that almost all of the corresponding entities (repos and branches) had been deleted from our jenkins instance. We suspect that the repos that were not deleted were preserved because they were building in Jenkins at the time of the Bitbucket Server outage. One of the negative outcomes from this is that all of our repos have been re-created in jenkins and the branches are starting with build 1. This isn't cool because we use the BUILD_TAG environment variable to uniquely identity build artifacts in various artifact repositories. So now our builds are all failing
[JIRA] (JENKINS-40699) Declarative pipeline beta docs: how to collect test results from different nodes
Title: Message Title Kevin Burnett commented on JENKINS-40699 Re: Declarative pipeline beta docs: how to collect test results from different nodes ok, so my specific use case can be solved by doing this instead of the code above in the sh instruction: bin/ci || true is adding "or true" so it doesn't abort execution before collecting test results the "right" solution? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40699) Declarative pipeline beta docs: how to collect test results from different nodes
Title: Message Title Kevin Burnett updated an issue Jenkins / JENKINS-40699 Declarative pipeline beta docs: how to collect test results from different nodes Change By: Kevin Burnett Summary: Declarative pipeline beta docs: how to collect test results from different nodes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40699) Declarative pipeline beta docs: how collect test results from different nodes
Title: Message Title
Kevin Burnett created an issue
Jenkins / JENKINS-40699
Declarative pipeline beta docs: how collect test results from different nodes
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/27 10:28 PM
Priority:
Minor
Reporter:
Kevin Burnett
If I want to run five different test suites, each having their own test result patterns, on five different nodes, in parallel, how do I do that? The abbreviated pipeline below all seems to work except for the collecting test results part, since when tests fail, the junit instruction is ignored (I guess since the previous step had a non-zero exit code). When not using the new declarative pipeline format, I could potentially use try/catch/finally and shove the junit instruction in the finally block as seen here. Current attempt:
pipeline {
agent label:'master'
environment {
GIT_COMMITTER_NAME = "jenkins"
GIT_COMMITTER_EMAIL = "jenk...@jenkins.io"
}
stages {
stage("Build") {
steps {
parallel (
"sweet" : {
node("has-docker") {
git 'ssh://g...@stash.example.com/automation/sweet.git'
sh 'APP_NAME=sweet \
TEST_ENV=qa5 \
bin/ci'
junit '**/test-reports/*.xml'
}
},
"word" : {
node("has-docker") {
git 'ssh://g...@stash.example.com/automation/word.git'
sh 'APP_NAME=word \
TEST_ENV=qa5 \
bin/ci'
junit '**/nosetests.xml'
}
}
)
}
}
}
post {
always {
deleteDir()
}
}
}
So in
