[JIRA] (JENKINS-50783) Support file based comments
Title: Message Title Alon Bar-Lev commented on JENKINS-50783 Re: Support file based comments That's great! I've read the documentation, and it looks nice, the use of draft and publish one time is good idea. The problem is that from documentation I do not understand how to install the plugin and if the current gerrit trigger plugin is required or not to trigger the job, I would like to remove the current plugin if possible. I also do not understand what component will eventually submit the draft comments. As there is no closure, I am unsure how a job which was not directly triggered can comment, for example, I have CI which runs only integration tests, it is not triggered directly from the review, but is aware of the review and like to put comments. I guess all the above are installation related and not per this specific feature. Thanks! 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-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann updated an issue Jenkins / JENKINS-54157 Unstable builds are marked as FAILED in Bitbucket Change By: Adrian Wyssmann Currently unstable builds in Jenkins are marked as failed in Bitbucket and I don't see a way how to configure it differently [https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/8c2c20f4443c11798a032a9f03523c73befd6296/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketBuildStatusNotifications.java#L119] !https://user-images.githubusercontent.com/15034009/47202372-364a1e80-d37d-11e8-9436-8918dde5af5d.png!There may be reasons why an unstable build still may be considered as "successful" in Bitbucket, even so the Jenkins build is unstable - i.e. you have a threshold set which allows certain tests to be failing but still consider the Jenkins test as not failed. The plugin should respect that.As such builds are considered failed, the code cannot be merged if the merge checks are available.The best solution would be to have a parameter "[ ] consider UNSTABLE builds as SUCCESS" where you can define the behavior - per team folder- jenkins wide 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
[JIRA] (JENKINS-54157) Unstable builds are marked as FAILED in Bitbucket
Title: Message Title Adrian Wyssmann updated an issue Jenkins / JENKINS-54157 Unstable builds are marked as FAILED in Bitbucket Change By: Adrian Wyssmann Currently unstable builds in Jenkins are marked as failed in Bitbucket and I don't see a way how to configure it differently!https://user-images.githubusercontent.com/15034009/47202372-364a1e80-d37d-11e8-9436-8918dde5af5d.png! There may be reasons why an unstable build still may be considered as "successful" in Bitbucket, even so the Jenkins build is unstable - i.e. you have a threshold set which allows certain tests to be failing but still consider the Jenkins test as not failed. The plugin should respect that.As such builds are considered failed, the code cannot be merged if the merge checks are available.The best solution would be to have a parameter "[ ] consider UNSTABLE builds as SUCCESS" where you can define the behavior- per team folder- jenkins wide 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-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. One of the reasons that I don't use 'Debian package builder' and I made my own(based off of jenkins-debian-glue) is because that particular Jenkins plugin doesn't use pbuilder in the correct way(it will run the pbuilder commands directly on your system, instead of actually making a chroot environment). So if something is working with debian-package-builder and not with debian-pbuilder, it is most likely a packaging problem. 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-50783) Support file based comments
Title: Message Title lucamilanesio updated JENKINS-50783 Jenkins / JENKINS-50783 Support file based comments Change By: lucamilanesio Status: In Progress Review 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-50783) Support file based comments
Title: Message Title lucamilanesio commented on JENKINS-50783 Re: Support file based comments https://github.com/jenkinsci/gerrit-code-review-plugin/pull/17 Code is under review 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Buffering at least to EOLs does not seem like it should be too hard. (You still need to send partial lines eventually.) And there are probably other sorts of tuning which could help here. First I need to analyze the attachments and see if I can devise a test case showing similar symptoms. 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Jesse Glick Component/s: durable-task-plugin Component/s: workflow-durable-task-step-plugin Component/s: workflow-job-plugin 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-54005) Trying to unexport an object that's already unexported (is back)
Title: Message Title Federico Naum commented on JENKINS-54005 Re: Trying to unexport an object that's already unexported (is back) Thank you! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50584) Scan Multibranch Pipeline Log fails
Title: Message Title lucamilanesio closed an issue as Duplicate Jenkins / JENKINS-50584 Scan Multibranch Pipeline Log fails Change By: lucamilanesio Status: In Progress Closed Resolution: Duplicate 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-50783) Support file based comments
Title: Message Title lucamilanesio commented on JENKINS-50783 Re: Support file based comments The way I am going to implement this will reflect the way you typically work with Gerrit: Add comments "as-you-go" and leave them in draft When review action is triggered on the change (the "Click Reply" button) then all the draft comments are published If you add comments in a set of parallel jobs controlled by the main one, then all the comments generated will be published together when the main job completes or fails. 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-50783) Support file based comments
Title: Message Title lucamilanesio started work on JENKINS-50783 Change By: lucamilanesio Status: Open In Progress 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-54070) Support for Jenkinsfile declarative pipelines
Title: Message Title lucamilanesio commented on JENKINS-54070 Re: Support for Jenkinsfile declarative pipelines https://github.com/jenkinsci/gerrit-code-review-plugin/pull/16 for review 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-54070) Support for Jenkinsfile declarative pipelines
Title: Message Title lucamilanesio updated JENKINS-54070 Jenkins / JENKINS-54070 Support for Jenkinsfile declarative pipelines Change By: lucamilanesio Status: In Progress Review 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-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Created https://github.com/jenkinsci/jira-plugin/pull/168 in hopes of getting this resolved 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-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen assigned an issue to Joseph Petersen Jenkins / JENKINS-52906 jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Change By: Joseph Petersen Assignee: Nicolas De Loof Joseph Petersen 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-52112) Private Gitea repositories are not visible
Title: Message Title Jan Breuer commented on JENKINS-52112 Re: Private Gitea repositories are not visible Private repositories are visible from jenkins gitea-plugin only to administrator accounts in Gitea. Creating administrator account where readonly access should be sufficiant is undesirable. It is also security risk, because in Jenkinsfile, there can be any code doing bad things to the repository. 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-54120) Output directory or source file null.
Title: Message Title
Christoph Loesch edited a comment on JENKINS-54120
Re: Output directory or source file null.
thanks, you're right, i forgot this one. now it seems to run through, but stops later.. ([seems to be a packaging problem| [https://github.com/mika/jenkins-debian-glue/issues/200 #issuecomment-431609562]] in olsrd .then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with : plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") {code:java}make[2]: Entering directory '/build/olsrd-0.9.6.1'mkdir -p /build/olsrd-0.9.6.1/debian/olsrd/usr/sbininstall -m 755 olsrd /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin: /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/olsrdif [ -e /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh ]; then \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new; \ echo "Policy routing script was saved as /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new"; \ else \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh; \ fi= C O N F I G U R A T I O N - F I L E olsrd uses the configfile /etc/olsrd/olsrd.confa default configfile. A sample RFC-compliance aimedconfigfile can be found in olsrd.conf.default.rfc.However none of the larger OLSRD using networks use thatso install a configfile with activated link quality exstensionsper default.can be found at files/olsrd.conf.default.lq==mkdir -p /etc/olsrdmkdir: cannot create directory '/etc/olsrd': Permission deniedmake[2]: *** [Makefile:177: install_olsrd] Error 1make[2]: Leaving directory '/build/olsrd-0.9.6.1'make[1]: *** [debian/rules:27: override_dh_auto_install] Error 2make[1]: Leaving directory '/build/olsrd-0.9.6.1'make: *** [debian/rules:15: binary] Error 2dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2E: Failed autobuilding of packageI: unmounting dev/ptmx filesystemI: unmounting dev/pts filesystemI: unmounting dev/shm filesystemI: unmounting proc filesystemI: unmounting sys filesystemI: Cleaning COW directoryI: forking: rm -rf /var/cache/pbuilder/build/cow.35458Build step 'Debian Pbuilder' marked build as failureFinished: FAILURE{code} then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") interesting also, when i try with architecture mipsel, it stops at another point, see log:[https://gist.github.com/vchrizz/7cde387c0c1ebdfc5efd68eef2879e6e]why does it stop here when apt should install packages?{code:java}...0 packages upgraded, 221 newly installed, 0 to remove and 0 not upgraded.Need to get 70.9 MB/93.8 MB of archives. After unpacking 364 MB will be used.Writing extended state information...E: pbuilder-satisfydepends failed.I: Copying back the cached apt archive contentsI: unmounting dev/ptmx filesystemI: unmounting dev/pts filesystemI: unmounting dev/shm filesystemI: unmounting proc filesystemI: unmounting sys filesystemI: Cleaning COW directoryI: forking: rm -rf /var/cache/pbuilder/build/cow.31117Build step 'Debian Pbuilder' marked build as failure{code}
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. thanks, you're right, i forgot this one. now it seems to run through, but stops later.. (seems to be a packaging problem in olsrd. then again, why does this work with plugin "Debian Package Builder" but not with plugin "Debian Pbuilder"? (as i can not crosscompile for other architectures with plugin "Debian Package Builder", i need to use plugin "Debian Pbuilder") make[2]: Entering directory '/build/olsrd-0.9.6.1' mkdir -p /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin install -m 755 olsrd /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin : /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/olsrd if [ -e /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh ]; then \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new; \ echo "Policy routing script was saved as /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh.new"; \ else \ cp -f files/sgw_policy_routing_setup.sh /build/olsrd-0.9.6.1/debian/olsrd/usr/sbin/sgw_policy_routing_setup.sh; \ fi = C O N F I G U R A T I O N - F I L E olsrd uses the configfile /etc/olsrd/olsrd.conf a default configfile. A sample RFC-compliance aimed configfile can be found in olsrd.conf.default.rfc. However none of the larger OLSRD using networks use that so install a configfile with activated link quality exstensions per default. can be found at files/olsrd.conf.default.lq == mkdir -p /etc/olsrd mkdir: cannot create directory '/etc/olsrd': Permission denied make[2]: *** [Makefile:177: install_olsrd] Error 1 make[2]: Leaving directory '/build/olsrd-0.9.6.1' make[1]: *** [debian/rules:27: override_dh_auto_install] Error 2 make[1]: Leaving directory '/build/olsrd-0.9.6.1' make: *** [debian/rules:15: binary] Error 2 dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 E: Failed autobuilding of package I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: Cleaning COW directory I: forking: rm -rf /var/cache/pbuilder/build/cow.35458 Build step 'Debian Pbuilder' marked build as failure Finished: FAILURE Add Comment
[JIRA] (JENKINS-54176) CLI AuthenticationCache is not working with -remoting + @CLIMethod
Title: Message Title
Wadeck Follonier updated an issue
Jenkins / JENKINS-54176
CLI AuthenticationCache is not working with -remoting + @CLIMethod
Change By:
Wadeck Follonier
When we use CLI commands like {{safe-restart}} or {{keep-build}}, the authentication cache provided by {{login}} in addition to {{-remoting}} is not working. It's due to the different way to manage those CLI commands compared to the regular one, that inherits from the {{CLICommand}} class.Example:Configure an instance with a user (login=user, password=user), and a project called "p".{code:bash}> java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting login --username user --password user> java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting build p> java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting keep-build p 1{code}The {{build}} will work but the {{keep-build}} will fail because the anonymous user does not have the Global {{Run / Read Update}} permission.
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-54176) CLI AuthenticationCache is not working with -remoting + @CLIMethod
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-54176 CLI AuthenticationCache is not working with -remoting + @CLIMethod Issue Type: Bug Assignee: Wadeck Follonier Components: cli, core Created: 2018-10-21 16:51 Priority: Trivial Reporter: Wadeck Follonier When we use CLI commands like safe-restart or keep-build, the authentication cache provided by login in addition to -remoting is not working. It's due to the different way to manage those CLI commands compared to the regular one, that inherits from the CLICommand class. Example: Configure an instance with a user (login=user, password=user), and a project called "p". > java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting login --username user --password user > java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting build p > java -jar jenkins-cli.jar -s http://localhost:8080/jenkins -remoting keep-build p 1 The build will work but the keep-build will fail because the anonymous user does not have the Global/Read permission.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Sharon George commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 I am also experiencing this at TFS plugin v5.133. is there any resolution? we cannot continue running tf delete each time this happens... Thanks, Sharon 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-54175) Job and auto-PR running npm audit fix
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54175 Job and auto-PR running npm audit fix Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-54175) Job and auto-PR running npm audit fix
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54175 Job and auto-PR running npm audit fix Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-21 13:42 Labels: security evergreen Priority: Minor Reporter: Baptiste Mathus Problem statement We need to regularly check security vulnerabilities. NPM has this nice npm audit fix command that can be run for this purpose that we then want to run regularly. Expected We should have a job that runs npm audit fix once per day for example, and files automatically a PR against the evergreen repo if there's an update available. Add Comment
[JIRA] (JENKINS-54174) Automate backend update PR
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54174 Automate backend update PR Change By: Baptiste Mathus Labels: newbie-friendly 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-54174) Automate backend update PR
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54174 Automate backend update PR Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-54174) Automate backend update PR
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-54174
Automate backend update PR
Change By:
Baptiste Mathus
h3. Problem statementCurrently, updating the backend is done manually through this kind of PRhttps://github.com/jenkins-infra/jenkins-infra/pull/1174h3. ExpectedThis PR should be filed automatically when a new backend is available (i . e. new image tag available at https://hub.docker.com/r/jenkinsciinfra/evergreen-backend/). Bonus point: maybe this PR should be created automatically only when there're changes in the services directory of evergreen (excluding on {{essentials.yaml}} and a few other files possibly).
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-54174) Automate backend update PR
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54174 Automate backend update PR Issue Type: Task Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-21 13:34 Priority: Minor Reporter: Baptiste Mathus Problem statement Currently, updating the backend is done manually through this kind of PR https://github.com/jenkins-infra/jenkins-infra/pull/1174 Expected This PR should be filed automatically when a new backend is available. Bonus point: maybe this PR should be created automatically only when there're changes in the services directory of evergreen (excluding on essentials.yaml and a few other files possibly). Add Comment
[JIRA] (JENKINS-53972) Octane needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53972 Octane needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-54094) Multiple octane tests are failing
Title: Message Title Daniel Gront updated JENKINS-54094 Jenkins / JENKINS-54094 Multiple octane tests are failing Change By: Daniel Gront Status: Fixed but Unreleased Reopened 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-53971) MC needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53971 MC needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53973) UFT needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53973 UFT needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53969) PC needs to change code structure
Title: Message Title Daniel Gront updated JENKINS-53969 Jenkins / JENKINS-53969 PC needs to change code structure Change By: Daniel Gront Status: In Review Closed Resolution: Postponed 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-53970) LR needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53970 LR needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53974) SV needs to change code strucutre
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53974 SV needs to change code strucutre Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53976) ALM needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53976 ALM needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53968) The hirearchy of the packages needs to change
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53968 The hirearchy of the packages needs to change Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53975) SRF needs to change code structure
Title: Message Title Daniel Gront closed an issue as Postponed Jenkins / JENKINS-53975 SRF needs to change code structure Change By: Daniel Gront Status: Open Closed Resolution: Postponed 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-53551) Map log levels sent to Sentry
Title: Message Title Baptiste Mathus updated JENKINS-53551 Jenkins / JENKINS-53551 Map log levels sent to Sentry Change By: Baptiste Mathus Status: In Progress Review 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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Andrei Brajnicov commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time Thank you for fast response. I will be happy to test a new version of this plugin. 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-53478) error 504 connecting Octane with Jenkins - Micro Focus Application Automation Tools
Title: Message Title Michael Seldin commented on JENKINS-53478 Re: error 504 connecting Octane with Jenkins - Micro Focus Application Automation Tools mariano costanzo, could you elaborate what security changes you made to jenkins? 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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Boguslaw Klimas commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time PR: https://github.com/jenkinsci/git-parameter-plugin/pull/72 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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Boguslaw Klimas commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time Hi, In this issue JENKINS-36833 I added synchronization block but after that I changed way to get branch or tag. Currently synchronization block is necessary only when the plugin getting revisions. I will try release plugin in this week 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-53940) Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53940 Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly Change By: Daniel Gront Labels: octane 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.
