[JIRA] (JENKINS-30778) Sauce Labs Test Publisher Configuration
Title: Message Title Mark Han commented on JENKINS-30778 Re: Sauce Labs Test Publisher Configuration 2019 and the same documentation still exists :\ the SauceOnDemandTestWatcher.java class helped. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165392.144388803.11350.1573240740219%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title
Mark Han commented on JENKINS-43353
Re: Ability to abort all previous running builds
Ended up not using Milestone because it doesn't communicate the build # that was stopped. Instead we're trying to use
def cancelPreviousBuilds() {
// Check for other instances of this particular build, cancel any that are older than the current one
def jobName = env.JOB_NAME
def currentBuildNumber = env.BUILD_NUMBER.toInteger()
def currentJob = Jenkins.instance.getItemByFullName(jobName)
// Loop through all instances of this particular job/branch
for (def build : currentJob.builds) {
if (build.isBuilding() && (build.number.toInteger() < currentBuildNumber)) {
echo "Older build still queued. Sending kill signal to build number: ${build.number}"
build.doStop()
}
}
}
If we put this outside of our node blocks, things are working well. We previously had this in a node{} which was horrible, and resolved the issue after you informing me of the heavyweight vs flyweight executors.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://g
[JIRA] (JENKINS-1878) Ability to move job to top of queue
Title: Message Title Mark Han commented on JENKINS-1878 Re: Ability to move job to top of queue Is the only way to get around this to cancel all queued items? How is this not a feature? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.131951.1213683192000.4.1570032901951%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Mark Han edited a comment on JENKINS-43353 Re: Ability to abort all previous running builds [~jglick] TIL about flyweight! This is helpful. In our recent past we have had issues in the past with milestones. *Scenario*: We have 7 PRs ready using Bitbucket, and 7 PR builds are queued up using the Multibranch Pipeline. After the first one of those gets merged, the other 6 have to rebuild because Develop was changed. However, a few of the previous runs are still trying to execute so a queue forms that looks something like this (Assuming there are multiple builds surrounding these that look similarly): *QUEUED JOBS:* ** part of Android-Build-Name >> PR-2715 #8part of Android-Build-Name >> PR-2715 #7 *RUNNING JOBS:*part of Android-Build-Name >> PR-2715 #6So, ideally we want to kill this running job #6 and the queued job #7 if a newer job #8 is queued up. Would something similar to line number 1 in the jenkinsfile for `jenkinsci/bom` solve this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180501.1491336786000.9805.1570030802181%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Mark Han commented on JENKINS-43353 Re: Ability to abort all previous running builds Jesse Glick TIL about flyweight! This is helpful. In our recent past we have had issues in the past with milestones. Scenario: We have 7 PRs ready using Bitbucket, and 7 PR builds are queued up using the Multibranch Pipeline. After the first one of those gets merged, the other 6 have to rebuild because Develop was changed. However, a few of the previous runs are still trying to execute so a queue forms that looks something like this (Assuming there are multiple builds surrounding these that look similarly): QUEUED JOBS: **part of Android-Build-Name >> PR-2715 #8 part of Android-Build-Name >> PR-2715 #7 RUNNING JOBS: part of Android-Build-Name >> PR-2715 #6 So, ideally we want to kill this running job #6 and the queued job #7 if a newer job #8 is queued up. Would something similar to line number 1 in the jenkinsfile for `jenkinsci/bom` solve this? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180501.1491336786000.9789.1570030801865%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Mark Han commented on JENKINS-43353 Re: Ability to abort all previous running builds We should make sure this change will allow for QUEUED builds to cancel RUNNING builds. We are running into a scenario where the amount of executors is limited, and the build server is being super congested by running out-of-date PR builds that should ideally be cancelled by the incoming queued PR builds. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180501.1491336786000.9055.1569944820399%40Atlassian.JIRA.
[JIRA] (JENKINS-27395) distinguish test reports filed from different parts of workflow
Title: Message Title Mark Han commented on JENKINS-27395 Re: distinguish test reports filed from different parts of workflow I think there's still a problem where running a simple `./gradlew test` merges all tests into one section, even though there can be multiple flavors of tests run. Not sure if this is the case if we explicitly break up the flavors e.g. `./gradlew testDebug` Do we need to break up `./gradlew` commands between separate stages? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161194.1426173157000.7464.1567741451672%40Atlassian.JIRA.
[JIRA] (JENKINS-53352) Consecutive white space is not rendered
Title: Message Title Mark Han edited a comment on JENKINS-53352 Re: Consecutive white space is not rendered Can we close this if listed as a included in 1.19 release of ? [https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.19.0] ? Or was this mistakenly added to release notes? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193436.1535642657000.7445.1567736880300%40Atlassian.JIRA.
[JIRA] (JENKINS-53352) Consecutive white space is not rendered
Title: Message Title Mark Han commented on JENKINS-53352 Re: Consecutive white space is not rendered Can we close this if listed as a release of https://github.com/jenkinsci/blueocean-plugin/releases/tag/blueocean-parent-1.19.0 ? Or was this mistakenly added to release notes? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193436.1535642657000.7443.1567736880274%40Atlassian.JIRA.
[JIRA] (JENKINS-50462) Artifacts tab presents everything as a flat list, making navigation time consuming
Title: Message Title Mark Han commented on JENKINS-50462 Re: Artifacts tab presents everything as a flat list, making navigation time consuming This is pretty frustrating. Any updates on if this is being improved, or a workaround would be appreciated. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189521.1522249108000.5541.1566233490451%40Atlassian.JIRA.
[JIRA] (JENKINS-58447) Cloud Foundry Plugin Error - Unable to upload to docker application
Title: Message Title Mark Han commented on JENKINS-58447 Re: Cloud Foundry Plugin Error - Unable to upload to docker application Seeing this exact same issue. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200579.1562858624000.10132.1565203380289%40Atlassian.JIRA.
[JIRA] (JENKINS-48315) Add env variable LAST_STAGE_NAME which will persist when stage ends prematurely
Title: Message Title Mark Han commented on JENKINS-48315 Re: Add env variable LAST_STAGE_NAME which will persist when stage ends prematurely Yea, this would be awesome for QOL 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186904.1512040368000.2043.1564164720326%40Atlassian.JIRA.
[JIRA] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Title: Message Title Mark Han commented on JENKINS-7139 Re: HtmlPublisher should be able to handle wildcard paths to find multiple html files Any update on this? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137236.1280999333000.16596.1563545941766%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
