[JIRA] (JENKINS-43546) Facing problem when integrating Blue Ocean with Bitbucket
Title: Message Title Joshua Noble assigned an issue to James Dumay Jenkins / JENKINS-43546 Facing problem when integrating Blue Ocean with Bitbucket Change By: Joshua Noble Assignee: Joshua Noble James Dumay 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-43546) Facing problem when integrating Blue Ocean with Bitbucket
Title: Message Title Joshua Noble assigned an issue to Joshua Noble Jenkins / JENKINS-43546 Facing problem when integrating Blue Ocean with Bitbucket Change By: Joshua Noble Assignee: James Dumay Joshua Noble 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-47823) withMaven fails to inject Maven settings files with docker-pipeline 1.14
Title: Message Title Joshua Noble commented on JENKINS-47823 Re: withMaven fails to inject Maven settings files with docker-pipeline 1.14 Josh Trow I know it's been a year, but I came up with a workaround for not having to update every mvn call here: https://issues.jenkins-ci.org/browse/JENKINS-40484?focusedCommentId=352635=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-352635 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Joshua Noble commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker I spent a good amount of time looking into this and came up with an acceptable workaround that works for my team. We have hundreds of branches across hundreds of repos, so updating all of the Java/Maven related Jenkinsfiles (on every branch) to use $MVN_CMD instead of "mvn" was not going to happen anytime soon. We also had several pending plugin updates, many of which required the latest version of the pipeline-maven plugin. In our case, we have a private internal Docker image that we use for all maven builds. It's forked off the official Docker Hub Maven image and includes a few additional tools and packages that we need. What I ended up doing was creating a bash script that simply wraps the "mvn" command and checks for existence of $MVN_CMD. If $MVN_CMD exists, it calls that and passes along the same parameters. If $MVN_CMD doesn't exist, it simply calls the real maven binary located at /usr/bin/mvn. This bash script lives at /usr/local/bin/mvn, which exists in our $PATH before the real maven binary, which is /usr/bin/mvn. Simply create a bash script like below, and ensure it has execute permissions: (chmod +x mvn.sh) #!/bin/bash if [[ -v MVN_CMD ]]; then $MVN_CMD "$@" else /usr/bin/mvn "$@" fi Then inside of your Dockerfile, add the following instruction: COPY mvn.sh /usr/local/bin/mvn This has been tested with the maven:3.5.3-jdk-8 Docker image. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I can confirm that setting up the Basic Branch Build Strategies plugin and selecting Regular Branches and Change Requests (with Ignore rebuilding merge branches checked) indeed gives us exactly what we want. Thanks for the tip! 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Joshua Noble commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker Any updates on this? 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-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Joshua Noble commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing I'm also looking for a way to exclude/ignore commits from a specific Git author. For example, an automated user who bumps the package.json version of an npm module. If that automated user pushes back to the repository after a build, that push will trigger yet another build. Is there a way to ignore/filter out events from certain commit authors? From what I can tell, the webhook events from GitHub include commit author information when a push occurs. 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-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble edited a comment on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up Isn't the whole point of a multibranch pipeline (within the context of the GitHub Branch Source plugin) to build multiple branches of the same origin? I don't see how adding multiple origins is a valid example. 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-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up Isn't the whole point of a multibranch pipeline to build multiple branches of the same origin? I don't see how adding multiple origins is a valid example. 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble edited a comment on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I'm also now seeing build storms from this issue.One can turn off "Periodically if not otherwise run" to prevent the storms, but then you're left with orphaned jobs being left behind when a branch is deleted. Therefore, if one tries to use the branch source plugin, they either have to deal with build storms, or with orphaned jobs. I don't think I saw this issue back when the core functionality existed in the GitHub Organization Folders plugin. Perhaps this is a regression? 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-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I'm also now seeing build storms from this issue. One can turn off "Periodically if not otherwise run" to prevent the storms, but then you're left with orphaned jobs being left behind when a branch is deleted. Therefore, if one tries to use the branch source plugin, they either have to deal with build storms, or with orphaned jobs. 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-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble reopened an issue Jenkins / JENKINS-42519 Closed pull requests, branch jobs are not cleaned up Change By: Joshua Noble Resolution: Not A Defect Status: Resolved Reopened Assignee: Stephen Connolly 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-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up I would like to bump this back up. Orphaned jobs should be deleted when an incoming webhook is received if the item strategy is set to 0. I also agree with Stephen Ash about JENKINS-37491. If a user wants to use GitHub Organization folders via the branch source plugin and build "merged" PR's, they either have to deal with build storms (by having "Periodically if not otherwise run" turned on) or deal with orphaned jobs. (By having "Periodically if not otherwise run" turned off, to prevent build storms) 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-31197) New jobs are not creating a new container
Title: Message Title Joshua Noble commented on JENKINS-31197 Re: New jobs are not creating a new container Dima Shmakov What version of Jenkins are you using? I tried your workaround with both the Throttle Concurrent and Single Use Slave plugins without any success. 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-31197) New jobs are not creating a new container
Title: Message Title Joshua Noble commented on JENKINS-31197 Re: New jobs are not creating a new container Any more movement on this issue? Given Docker's ephemeral nature we really should modify this plugin to fulfill the OP's request, as it also matches my own. We should be able to spin up multiple new slaves via ECS tasks for the same label. Currently only one slave can run at a time per label - that's a significant bottleneck. Would this logic be contained within this plugin's source - or within the Jenkins core? If someone could point me in the right direction, I might be able to attempt to spend a few cycles on this. Thanks! 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.
