[JIRA] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel updated an issue Jenkins / JENKINS-32279 OWASP Dependency-Check Plugin ignores supressions Change By: Markus Schlegel Attachment: configuration.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance (Praqma case 14102)
Title: Message Title Thierry Lacour updated an issue Jenkins / JENKINS-32383 Java 1.6 compliance (Praqma case 14102) Change By: Thierry Lacour Summary: Java 1.6 compliance (Praqma case 14102) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xcode-plugin] (JENKINS-32380) can't build ios Project which has two targets and has the different sign
Title: Message Title Thieven Zhai created an issue Jenkins / JENKINS-32380 can't build ios Project which has two targets and has the different sign Issue Type: Bug Assignee: Unassigned Attachments: TVGuor.rar Components: xcode-plugin Created: 11/Jan/16 2:01 AM Environment: Jenkins(ubuntu)+Mac OS(Slave)+Xcode integration plug Jenkins ver. 1.568 Xcode integration 1.4.9 Priority: Blocker Reporter: Thieven Zhai Hi:Sir Firstly ,thanks for your support.we have an iOS App project,we want jenkins+xcode integration to dailybuild the ios app. The iOS app project has two target ,one is extention target:"Today", it is the embedded binaries,the two target has different buddle id and profile,how to config the xcode integ ration plug? thanks
[JIRA] [update-sites-manager-plugin] (JENKINS-32376) Private certifacates doesn't work with server-based download (Jenkins >= 1.557)
Title: Message Title ikedam started work on JENKINS-32376 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xcode-plugin] (JENKINS-32380) can't build ios Project which has two targets and has the different buddle id and profile
Title: Message Title Thieven Zhai updated an issue Jenkins / JENKINS-32380 can't build ios Project which has two targets and has the different buddle id and profile Change By: Thieven Zhai Summary: can't build ios Project which has two targets and has the different sign buddle id and profile Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [update-sites-manager-plugin] (JENKINS-32376) Private certifacates doesn't work with server-based download (Jenkins >= 1.557)
Title: Message Title ikedam commented on JENKINS-32376 Re: Private certifacates doesn't work with server-based download (Jenkins >= 1.557) > To clarify, this also happens when specifying a certification with the custom update site? Exactly. The process injecting the specified certificate isn't performed in server-based download. That process is implemented as wrapper of UpdateSite#doPostBack, which is for client-based download and not invoked for server-based download. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [update-sites-manager-plugin] (JENKINS-32376) Private certifacates doesn't work with server-based download (Jenkins >= 1.557)
Title: Message Title ikedam commented on JENKINS-32376 Re: Private certifacates doesn't work with server-based download (Jenkins >= 1.557) https://github.com/jenkinsci/update-sites-manager-plugin/pull/3 https://github.com/jenkinsci/update-sites-manager-plugin/pull/5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [xcode-plugin] (JENKINS-32380) can't build ios Project which has two targets and has the different sign
Title: Message Title Thieven Zhai updated an issue Jenkins / JENKINS-32380 can't build ios Project which has two targets and has the different sign Change By: Thieven Zhai Hi:Sir Firstly ,thanks for your support.we have an iOS App project,we want jenkins+xcode integration to dailybuild the ios app. The iOS app project has two target ,one is extention target:"Today", it is the embedded binaries,the two target has different buddle id and profile,how to config the xcode integration integration plug? thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee created an issue Jenkins / JENKINS-32381 Add git global configuration option Issue Type: Bug Assignee: Makson Lee Components: repo-plugin Created: 11/Jan/16 6:15 AM Priority: Minor Reporter: Makson Lee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee updated an issue Jenkins / JENKINS-32381 Add git global configuration option Change By: Makson Lee Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee started work on JENKINS-32381 Change By: Makson Lee Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee updated an issue Jenkins / JENKINS-32381 Add git global configuration option Change By: Makson Lee We need an option to provide git configuration before each run of job. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee commented on JENKINS-32381 Re: Add git global configuration option https://github.com/jenkinsci/repo-plugin/pull/29 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [repo-plugin] (JENKINS-32381) Add git global configuration option
Title: Message Title Makson Lee closed an issue as Done Jenkins / JENKINS-32381 Add git global configuration option Change By: Makson Lee Status: In Progress Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [mask-passwords-plugin] (JENKINS-32382) Non-ASCII characters in the console output will be gibberish when apply mask passwords in the Job
Title: Message Title Ahlfors Lee created an issue Jenkins / JENKINS-32382 Non-ASCII characters in the console output will be gibberish when apply mask passwords in the Job Issue Type: Bug Assignee: Oleg Nenashev Attachments: plug.JPG, right.JPG, wrong.JPG Components: mask-passwords-plugin Created: 11/Jan/16 6:44 AM Environment: Jenkins Version:1.625.3 Mask Passwords Plugin Version: 2.8 Priority: Major Reporter: Ahlfors Lee Non-ASCII characters in the console output will be gibberish when apply mask passwords in the Job. If applied: The console output will be: If removed, it will back to normal:
[JIRA] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Thomas Blitz commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation Great news about the postfix on initial commit. I am very happy and it is going to save us many hours and irritation. Then to my idea that i would like to quickly hear your thoughts about. Scenario. When we f.ex. delete branches the plugin does delete the project in Jenkins, and that is nice. WE do however also have a number of subsystems, with API's, that also needs information about the delete. So far we handle this manually and do the actions required by hand. We could however automate it with scripts. So the idea is to be able to trigger a script upon a delete in gitlab via the plugin. Simplest scenario is that on every commit the gitlab plugin will allow a kind of a chain where it will push the commit information to some kind of script runner. Something very generic. I can argue that allowing the gitlab plugin to implement this feature could be wrong. Should this really be there. I could argue that maybe i should make a new plugin, that also get triggered via a webhook in gitlab and then it can run scripts. So a quick yes or no from you Do you think that the gitlab plugin could/should have the ability to trigger some kind of script mechanism or should it be in a separate new plugin. The main reason for choosing the gitlab plugin would be the infrastructure that is already present in you code for webhook handling and processing of the webhook information. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-31128) Add Matrix Project compatibility (our case 13748)
Title: Message Title Thierry Lacour updated an issue Jenkins / JENKINS-31128 Add Matrix Project compatibility (our case 13748) Change By: Thierry Lacour Summary: Add Matrix Project compatability compatibility (our case 13748) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [dependency-check-jenkins-plugin] (JENKINS-32279) OWASP Dependency-Check Plugin ignores supressions
Title: Message Title Markus Schlegel updated an issue Jenkins / JENKINS-32279 OWASP Dependency-Check Plugin ignores supressions Our suppression file, where the content is ignored. Change By: Markus Schlegel Attachment: OWASP-Dependency-Check-Suppression.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [negotiate-sso-plugin] (JENKINS-32365) Repeating URL Redirection
Title: Message Title
Florian Huber commented on JENKINS-32365
Re: Repeating URL Redirection
Hi,
it happens on both urls.
The SPN for the Computer Object are the following: {{setspn -L ci01 Registered ServicePrincipalNames for CN=CI01,OU=Member Server,DC=example,DC=local: HTTP/ci01 HTTP/ci01.example.local TERMSRV/CI01 TERMSRV/ci01.example.local RestrictedKrbHost/CI01 HOST/CI01 RestrictedKrbHost/ci01.example.local HOST/ci01.example.local }}
Kerberos Delegation is unset:
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [negotiate-sso-plugin] (JENKINS-32365) Repeating URL Redirection
Title: Message Title Florian Huber updated an issue Jenkins / JENKINS-32365 Repeating URL Redirection Change By: Florian Huber Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [pretested-integration-plugin] (JENKINS-32383) Java 1.6 compliance
Title: Message Title Thierry Lacour created an issue Jenkins / JENKINS-32383 Java 1.6 compliance Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 11/Jan/16 7:39 AM Priority: Minor Reporter: Thierry Lacour Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups
[JIRA] [image-gallery-plugin] (JENKINS-31364) Image width is set to "0" in previous builds
Title: Message Title Bruno P. Kinoshita started work on JENKINS-31364 Change By: Bruno P. Kinoshita Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies
Title: Message Title evernat assigned an issue to Unassigned Jenkins / JENKINS-32377 Upgrade Jetty to fix bugs in cookies Change By: evernat Assignee: Ulli Hafner Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [image-gallery-plugin] (JENKINS-31364) Image width is set to "0" in previous builds
Title: Message Title Bruno P. Kinoshita commented on JENKINS-31364 Re: Image width is set to "0" in previous builds Hi! I couldn't reproduce this issue. Here's the steps I tried: Started the plug-in with Jenkins 1.580.3 (git clone repository + mvn hpi:run) Created a simple job with one Execute Shell build step: `wget http://i.imgur.com/d8Y0tS8.png` Added post build action to archive *.png Added post build action to create an image gallery Selected Archived Images Gallery, Gallery title => Test 1, Include pattern => *.png Building the project the image is downloaded and archived, and I can see the image + gallery on the first build page. Building the project again, generates build #2. I can see the image on the build page of both builds just fine. Not sure if I should have chosen a different gallery, or if there is something else that could highlight why I couldn't reproduce it. Should be easy to fix once we find what's broken Cheers Bruno Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [image-gallery-plugin] (JENKINS-31364) Image width is set to "0" in previous builds
Title: Message Title Bruno P. Kinoshita stopped work on JENKINS-31364 Change By: Bruno P. Kinoshita Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30322) Gitlab Notifier not firing
Title: Message Title Javier Palacios started work on JENKINS-30322 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30322) Gitlab Notifier not firing
Title: Message Title Javier Palacios commented on JENKINS-30322 Re: Gitlab Notifier not firing The 'api/v3' has been removed from documentation. But you are right that there is no clear indication on the job log for the notifier. At the very end of the log you might see a message like [workspace] $ git log -1 --oneline --format=%P but it only serve to check that it was fired (I'll add some real feedback for the posting result). I believe that the important point is that reporter permission could not be enough, as the user must be capable of adding comments to a commit (see this for example). If you increase the privileges of the user, it will probably work. But with standard gitlab this feature is on my believe more useful for reporting to merge requests, and maybe there reporter permission could suffice. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27977 Re: NullPointer & authentication cancelled occure immediately on SVN checkout Tim Styles, Please, file a new issue with your environment and configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27977) NullPointer & authentication cancelled occure immediately on SVN checkout
Title: Message Title Manuel Jesús Recena Soto closed an issue as Cannot Reproduce Jenkins / JENKINS-27977 NullPointer & authentication cancelled occure immediately on SVN checkout Change By: Manuel Jesús Recena Soto Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30861) Ignore 'Polling ignores commits from certain users' on GitLab WebHooks
Title: Message Title Javier Palacios resolved as Postponed Jenkins / JENKINS-30861 Ignore 'Polling ignores commits from certain users' on GitLab WebHooks Change By: Javier Palacios Status: Open Resolved Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30861) Ignore 'Polling ignores commits from certain users' on GitLab WebHooks
Title: Message Title Javier Palacios commented on JENKINS-30861 Re: Ignore 'Polling ignores commits from certain users' on GitLab WebHooks This is actually an issue with gitlab-hook design. It searchs for projects with matching repository url, and apart for the branch and refspec checks, no other configuration item from git-plugin is considered. Neither ignored users, nor ignored paths nor anything else. The reason behind is that is implemented on ruby, and there is no actual triggers on jruby-jenkins, so the plugin is actually a jenkins RootAction. I've done some steps toward it, but it's not yet ready, so this will take some time to get fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28452) Push event web hook triggers all jobs regardless of Branch Specifier
Title: Message Title Javier Palacios closed an issue as Fixed I sould fix write permission on the plugins store, but 1.4.1 will be available in a few days. Jenkins / JENKINS-28452 Push event web hook triggers all jobs regardless of Branch Specifier Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Title: Message Title Javier Palacios closed an issue as Fixed Jenkins / JENKINS-25267 Gitlab hook not building on merge request object Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-31179) Gitlab web hook is not working.
Title: Message Title Javier Palacios resolved as Cannot Reproduce Jenkins / JENKINS-31179 Gitlab web hook is not working. Change By: Javier Palacios Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29283) Allow cloning job trees when creating job via gitlab web hook
Title: Message Title Javier Palacios commented on JENKINS-29283 Re: Allow cloning job trees when creating job via gitlab web hook If I understand right, you would like that when a project is created for a new branch, not "clone" only the main job, but all the multijob pack. As I said in the related issue, have no knowledge on multijob so, could you attach the config.xml for a pack? I'll try to add it to acceptance tests to see the behaviour. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29283) Allow cloning job trees when creating job via gitlab web hook
Title: Message Title Javier Palacios resolved as Won't Do Jenkins / JENKINS-29283 Allow cloning job trees when creating job via gitlab web hook Change By: Javier Palacios Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29318) Support deleting multiple jobs on branch delete
Title: Message Title Vladimir Sitnikov commented on JENKINS-29318 Re: Support deleting multiple jobs on branch delete This is an additional feature to JENKINS-29317. In other words, it might make sense to configure things like "trigger jobs A,B on push, C,D on delete, etc". However, I would be fine if the same job is triggered on push/delete provided there is a parameter that identifies the source event (push, deleted branch, etc). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved
Title: Message Title Ulli Hafner commented on JENKINS-25917 Re: Spaces in URL (from project name or view) cause invalid cookies to be saved Thanks for finding the actual reason! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [analysis-core-plugin] (JENKINS-25917) Spaces in URL (from project name or view) cause invalid cookies to be saved
Title: Message Title evernat commented on JENKINS-25917 Re: Spaces in URL (from project name or view) cause invalid cookies to be saved yes, cookie path is correct and http header "Set-Cookie" received by the browser seems also correct: Server Jetty(winstone-2.9) Set-Cookie TestResultAction_failureOnly=false;Path="/job/project%20with%20spaces";Expires=Mon, 09-Jan-2017 11:27:25 GMT But the cookie is not saved correctly by the browser (Chrome and Firefox), certainly because of quotes in the Path. It happens that Jenkins uses Jetty 8.1.13 (https://github.com/jenkinsci/winstone/blob/master/pom.xml#L221) which is buggy (see here and here) It will be needed to upgrade Jetty to 9.0.6 or later. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-25267) Gitlab hook not building on merge request object
Title: Message Title Javier Palacios resolved as Fixed I've opened an issue specific for http repositories Jenkins / JENKINS-25267 Gitlab hook not building on merge request object Change By: Javier Palacios Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url I've no experience with multijob projects, but the plugin does search projects that match the repository url, so if your phase 2 & 3 are triggered, it is because they also clone your git repository. Your suggestion is not bad, but it breaks everything else, as every job created manually will stop building on pushes. A configuration item could be added to enable this "only autocreated" behaviour, but I would like to understand your use case before attempting it. Regarding your second suggestion, if I understand it well, has the same problem of your current modification, and forces to name the project as the repository, and although it's probably happening with most cases, nothing guarantees that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29283) Allow cloning job trees when creating job via gitlab web hook
Title: Message Title Vladimir Sitnikov commented on JENKINS-29283 Re: Allow cloning job trees when creating job via gitlab web hook Finally, I gave up with Job Copy, job cloning, etc, so this issue can probably be closed. Job cloning has too much constraints. I ended up with using Job DSL for programmatic job creation. The case is explained here: https://issues.jenkins-ci.org/browse/JENKINS-29317?focusedCommentId=245505=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-245505 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url Yes, it does make a lot of sense, but I'm not sure if it's doable in the context of this plugin. It basically depends on how non-build phases are done. I'll tell you the flow I used for this same scenario, although the config.xml of the jobs is still useful to fully understand your flow. In my case, I have a single environment where to deploy artifacts and run the tests. Everything was built as debian packages, so I got an additional element, but I don't believe it is important. The build job was the only one that performed a git clone, and also to deploy the package to a repository which was the same for all the jobs. The deploy & test part was a bit complex, but there was a single set of them, and the connection was done with the standard jenkins triggering. This was a bit o a mesh, as concurrent builds are very dangerous, and in any case the flow graph was a bit ugly, but fortunately every repository used to have only one developer working on it (although there were plenty of repositories, libraries triggering other jobs and stuff like that). And tracking which builds introduced which error was far from being straightforward. But I had separated (multiple) phase 1, and single unified later phases. If your deploy & test phases must be multiple ones (maybe a full environment is deployed for them), I would suggest to write all those parts into the phase 1 job, to get a single job that could be easily cloned. But when I get a bit of time I will look to multijob, because there should be some link among them within the project configuration. In the long term, I've made some attempts towards a real trigger, that should be configured not on global jenkins configuration, but enabled on every job. And at some point in that (not short) path there is probably a solution for your problem, as you could just select your seed project as the only one to be considered. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios updated an issue Jenkins / JENKINS-29317 Trigger only autogenerated jobs, not all the jobs for given git url Change By: Javier Palacios Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29309) Jenkins cannot start with gitlab-hook plugin
Title: Message Title Javier Palacios commented on JENKINS-29309 Re: Jenkins cannot start with gitlab-hook plugin Apologies for the delay, but I've been off for a few months. Could you post the full startup log? The part you posted related to the plugin seems ok Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30061) Can't get build status on GitLab Merge Request
Title: Message Title
Javier Palacios commented on JENKINS-30061
Re: Can't get build status on GitLab Merge Request
Apologies for the long delay, but I've been a bit apart of this project for a few months. I believe what you are seeing is an exception while capturing an exception. Around line 63 of $JENKINS_HOME/plugins/gitlab-hook/WEB-INF/classes/models/api.rb you should get this block:
rescue => e
# avoid method signature warnings
severe = logger.java_method(:log, [Level, java.lang.String, java.lang.Throwable])
severe.call(Level::SEVERE, e.message, RaiseException.new(e))
status 500
[e.message, '', 'Stack trace:', e.backtrace].flatten.join('')
end
Replacing with
rescue => e
logger.warning(e.message)
logger.warning(e.backtrace.join("\n" )
status 500
end
should (after restarting) give the real error
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [analysis-core-plugin] (JENKINS-32377) Upgrade Jetty to fix bugs in cookies
Title: Message Title evernat created an issue Jenkins / JENKINS-32377 Upgrade Jetty to fix bugs in cookies Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin, core, junit-plugin, winstone-jetty Created: 10/Jan/16 12:03 PM Priority: Major Reporter: evernat Jetty is causing bugs in junit and analysis graphs because of cookies for paths with whitespaces. See JENKINS-25917 Jenkins uses Jetty 8.1.13 (https://github.com/jenkinsci/winstone/blob/master/pom.xml#L221) which is buggy (see here and here) It is needed to upgrade Jetty to 9.0.6 or later. Add Comment
[JIRA] [gitlab-hook-plugin] (JENKINS-32378) Trigger build when the url is an http/https one
Title: Message Title Javier Palacios created an issue Jenkins / JENKINS-32378 Trigger build when the url is an http/https one Issue Type: New Feature Assignee: Javier Palacios Components: gitlab-hook-plugin Created: 10/Jan/16 12:32 PM Priority: Major Reporter: Javier Palacios Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [gitlab-hook-plugin] (JENKINS-27101) Undefined method isOlderThan on automatic project creation
Title: Message Title Javier Palacios closed an issue as Fixed Jenkins / JENKINS-27101 Undefined method isOlderThan on automatic project creation Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-plugin] (JENKINS-23992) Jenkins git-plugin not parsing HTML in build reason
Title: Message Title Javier Palacios closed an issue as Fixed Jenkins / JENKINS-23992 Jenkins git-plugin not parsing HTML in build reason Change By: Javier Palacios Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29309) Jenkins cannot start with gitlab-hook plugin
Title: Message Title Javier Palacios resolved as Cannot Reproduce I see you are using 1.609, could you test with some of the latest LTS versions or current one (1.643). According to TravisCI, it works on them. Jenkins / JENKINS-29309 Jenkins cannot start with gitlab-hook plugin Change By: Javier Palacios Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28808) 'undefined method `extensions'' on processing Multiple SCMs projects
Title: Message Title Javier Palacios started work on JENKINS-28808 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28808) 'undefined method `extensions'' on processing Multiple SCMs projects
Title: Message Title Javier Palacios commented on JENKINS-28808 Re: 'undefined method `extensions'' on processing Multiple SCMs projects Could someone post a config.xml for a multi-scm project? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30861) Ignore 'Polling ignores commits from certain users' on GitLab WebHooks
Title: Message Title Javier Palacios updated an issue Jenkins / JENKINS-30861 Ignore 'Polling ignores commits from certain users' on GitLab WebHooks Change By: Javier Palacios Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Vladimir Sitnikov commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url Javier Palacios, my case is as follows: 1) I have a project at Gitlab. Suppose it is named "ProjectFoo". 2) I want each branch to spawn a dedicated Jenkins job. The intention is as follows: each developer works in his/her own branch, thus having separate Jenkins jobs helps a lot. However, the build process itself is not that simple. Basically it includes several stages: S1) Fetch & compile project S2) Prepare database (each test is to be executed in a clean environment, thus each job execution gets its own database schema) S3) Deploy the code (run installation SQL scripts, etc, etc) S4) Execute fast tests (if they fail, no need to run full suite) S5) Execute full suite of tests (here additional DB instances are provisioned to test against different DB versions, etc) S6) Uninstall (to test uninstall) I think it is somewhat typical scenario for integration tests. In order to simplify management of those integration jobs, I use Job DSL plugin. In other words, I have a "seed job" that generates all those S1, S2, ..., S3 given the input parameters like "branch name", "DB versions to test", etc. The "seed job" has just a single step: "invoke groovy script". Job management via groovy scripts turned out to be very efficient. So my end-to-end is: E1) A developer pushes commit to Gitlab E2) Gitlab notifies Jenkins. Here only seed job should be triggered. E3) Seed job fetches project sources, figures out the proper set of integration jobs, creates/updates as required, then triggers the actual integration testing. The problem is at step E2 my Jenkins server has lots of jobs with given GIT project URL. For each project I have exactly one seed job, so I do not want to trigger all of them. Does that make sense? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title
Vladimir Sitnikov edited a comment on JENKINS-29317
Re: Trigger only autogenerated jobs, not all the jobs for given git url
I have lots of jobs that access git for different reasons:0) "seed job" to get "integration configuration"1) compile job to compile the project2) test job to get test sourcesetc, etc.In other words, what I want from Gitlab-Jenkins integration is that the plugin triggers ONLY the seed job.I'm fine to set " build trigger job in case of gitlab push" kind of flag on a seed job.{quote} connection was done with the standard jenkins triggering{quote}Multijob connection enables to have:1) Single status view of each step2) Single "stop all" button3) Nice "cleanup if anything went wrong" steps4) etc, etc.However multijob stuff is completely irrelevant for the particular issue. The issue is to have an ability to limit the set of triggered jobs. Why trigger all the jobs with given url?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [build-user-vars-plugin] (JENKINS-14490) Build User Variables should be accessible from Post-Build Actions
Title: Message Title Yaron Golan commented on JENKINS-14490 Re: Build User Variables should be accessible from Post-Build Actions Same as in the post build step named "Editable Email notification". The variables are not parsed. Any workaround I can use? TIA, Yargo Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30861) Ignore 'Polling ignores commits from certain users' on GitLab WebHooks
Title: Message Title Javier Palacios assigned an issue to Javier Palacios Jenkins / JENKINS-30861 Ignore 'Polling ignores commits from certain users' on GitLab WebHooks Change By: Javier Palacios Assignee: Javier Palacios Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-31179) Gitlab web hook is not working.
Title: Message Title Javier Palacios commented on JENKINS-31179 Re: Gitlab web hook is not working. You could check with 1.4.0 or latest snapshot (from http://repo.jenkins-ci.org/snapshots/org/jenkins-ci/ruby-plugins/gitlab-hook/1.4.1-SNAPSHOT/), but I don't believe it makes a change, and looks like an issue with proxy settings. All your info seems related to gitlab part, and until the communication doesn't hit jenkins, I cannot say anything. Assuming you are using your own gitlab instance, it could be faster test connectivity from command line. Regarding the uncompatible working versions, I've added recent builds to travisci. It works on latest LTS (1.625.3), and also on latest release (1.643). Looks like it was an issue related to jruby-jenkins integration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29283) Allow cloning job trees when creating job via gitlab web hook
Title: Message Title Javier Palacios updated an issue Jenkins / JENKINS-29283 Allow cloning job trees when creating job via gitlab web hook Change By: Javier Palacios Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url However multijob stuff is completely irrelevant for the particular issue. The issue is to have an ability to limit the set of triggered jobs. Why trigger all the jobs with given url? That's a matter of design. The plugin is not actually a Trigger object, but a RootAction one. It allows to use the same url on all gitlab repositories, but reduces the number of project specific things that can be done (in particular, most of advanced features of git plugin are not honoured). My plans for trigger alike behaviour will overcome this limitation, but it is not a matter of weeks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation I'll check the documentation, but that is the expected behaviour. Although both projects get created automatically, they follow quite different paths. When it receives an unknown branch for a known repository, it uses the existing job as base, but when the notification is for a completely unknown repository, it is created from a template. On the first case, there is a configuration flag to select whether the new project is prefixed with the repository name or with the name of the "cloned" project. On the second case only the repository name can be used and no branch name is suffixed because the assumption is that this first push is for the master branch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios resolved as Not A Defect Jenkins / JENKINS-28973 naming autogenerated project does not postfix with branchname on first creation Change By: Javier Palacios Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-30061) Can't get build status on GitLab Merge Request
Title: Message Title Javier Palacios started work on JENKINS-30061 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Vladimir Sitnikov commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url I have lots of jobs that access git for different reasons: 0) "seed job" to get "integration configuration" 1) compile job to compile the project 2) test job to get test sources etc, etc. In other words, what I want from Gitlab-Jenkins integration is that the plugin triggers ONLY the seed job. I'm fine to set "build job in case of gitlab push" kind of flag on a seed job. connection was done with the standard jenkins triggering Multijob connection enables to have: 1) Single status view of each step 2) Single "stop all" button 3) Nice "cleanup if anything went wrong" steps 4) etc, etc. However multijob stuff is completely irrelevant for the particular issue. The issue is to have an ability to limit the set of triggered jobs. Why trigger all the jobs with given url? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29318) Support deleting multiple jobs on branch delete
Title: Message Title Javier Palacios commented on JENKINS-29318 Re: Support deleting multiple jobs on branch delete Can I assume this is the counter part of JENKINS-29283 ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-24278) Node monitor for free inodes
Title: Message Title Baptiste Mathus commented on JENKINS-24278 Re: Node monitor for free inodes Hi, just pushed https://github.com/batmat/inodes-monitor-plugin what do you think? Should it be left as a plugin (still to be forked, if deemed useful), or be proposed to core? (why I'm not marking this issue fixed yet) The advantage of it being a plugin is that it can be used immediately on older Jenkins. But it would also be very useful that Jenkins offers that out of the box, just like disk space monitoring (as Daniel Beck says above, it's just as important. Running out of inodes will have just the same effect). Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Thomas Blitz updated an issue Jenkins / JENKINS-28973 naming autogenerated project does not postfix with branchname on first creation Change By: Thomas Blitz Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Serg Pr assigned an issue to Mark Waite Sorry. Next time I will create "task" instead of "bug". Also I found error in my configuration. I used "github url". I disabled it and add url to "bitbucket browser". Thanks a lot and sorry again! Jenkins / JENKINS-32186 bad links to bitbucket Change By: Serg Pr Assignee: Nicolas De Loof Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Serg Pr updated an issue Jenkins / JENKINS-32186 bad links to bitbucket Change By: Serg Pr Comment: Sorry. Next time I will create "task" instead of "bug".Also I found error in my configuration.I used "github url". I disabled it and add url to "bitbucket browser".Thanks a lot and sorry again! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32358) Installing multiple plugins using "install-plugin" jenkins CLI command
Title: Message Title Daniel Beck commented on JENKINS-32358 Re: Installing multiple plugins using "install-plugin" jenkins CLI command Downside is that you'd have to enter the passphrase many times. Workaround would be to use the CLI over SSH. Would be a lot faster too, I expect. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios started work on JENKINS-29317 Change By: Javier Palacios Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation Yes, it's written in ruby (or jruby, which is even a bit worse ...) 1. You commit to ex. master for repo FOO, and the plugin creates a new project in Jenkins because the repo is unknown.. The project is named something like FOO in jenkins, even thou the branch is master. 2. You commit to master of FOO again. The plugin creates a NEW project called: FOO_master which is based on the project FOO. I argue that the first time a project is created it should also be postfixed with the branch since this is the behaviour it will do afterwards on all commits to any branch. If that is the behaviour you see, then it is a real bug. Point 2 should happen, because the plugin should discover that there is a project already tracking master branch, and will schedule a build for it instead of creating a new one. And if it happens, it should happen also if project name is postfixed, because it reads branchspec from git configuration, not the project name. And in that case, you will end with FOO_master_master_master after a while. I saw that behaviour at some point in the past, although I believe only in development version. In any case, I'm publishing a new release (1.4.1.1) with a few fixes done long time ago. Please try it and tell me if this issue still applies. The new release will take some time to appear on update center, but you can get it the latest snapshot from http://maven.jenkins-ci.org/content/repositories/snapshots/org/jenkins-ci/ruby-plugins/gitlab-hook/1.4.1-SNAPSHOT/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [core] (JENKINS-24278) Node monitor for free inodes
Title: Message Title Oleg Nenashev commented on JENKINS-24278 Re: Node monitor for free inodes Baptiste Mathus I would vote for integrating it into Jenkins core or disk usage plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Thomas Blitz commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation No, you misunderstand me. Let be clarify. Scenario 1. Repo FOO is unknown to the plugin. Behaviour. On commit to branch ex. master the plugin recieves the commit via webhook. Then it creates a Jenkins project named FOO. No postfix of branch master (as i argue it should) Scenario 2. Repo FOO has been thru Scenario 1 and that is the current state. Behaviour. On second commit to master branch of FOO the plugin recieves the commit via webhook. Then it creates a new project named: FOO_master based on the previous project named FOO. This is expected and all is ok, because the plugin bases the new project on a previous one. Scenario 3. Repo FOO recieves a third commit to master. Behaviour. The plugin does not create a new project named FOO_master_master but simply triggers FOO_master. This is the expected behaviour. Scenario 4. Repo FOO recieves commit to ex. develop branch. Behaviour: The plugin creates a new project named: FOO_develop and bases it on a previous project that has the basename of FOO. This is expected. So i simply want it to start out by postfixing the branchname even when the Repo is unknown in jenkins. I hope that clarifies any misunderstandings ps. If you are the developer on this plugin i have an idea i would like to discuss with you, if you have 5 minutes for that maybe skype text chat? Regards Thomas Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Serg Pr commented on JENKINS-32186 Re: bad links to bitbucket Sorry. Next time I will create "task" instead of "bug". Also I found error in my configuration. I used "github url". I disabled it and add url to "bitbucket browser". Thanks a lot and sorry again! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Thomas Blitz reopened an issue I think that the 'expected' behaviour is counter intuitive. I understand the different paths but the goal should be the same, namely: 1. Create projects 2. postfix with branch name, independant of if the repo is unknown or not. Then there is no unnecessary manually work required, as explained below. These two goals should always be upheld in all cases. We can safely assume that there will always be a branch associated with a commit so the branch name should be postfixed. The issue above has the undesired outcome that: 1. You commit to ex. master for repo FOO, and the plugin creates a new project in Jenkins because the repo is unknown.. The project is named something like FOO in jenkins, even thou the branch is master. 2. You commit to master of FOO again. The plugin creates a NEW project called: FOO_master which is based on the project FOO. I argue that the first time a project is created it should also be postfixed with the branch since this is the behaviour it will do afterwards on all commits to any branch. At least allow it to be a settable property on the plugin. The outcome in our env. is that after we commit the first time and the plugin creates the base, non postfixed repo, we then immediately commit again, allow the plugin to create yet another project that has the branch postfix, and then we have to delete the original non postfixed project - manually, thus automation fails in this case. I will change the type from bug to feature request, since i can understand from you that the the current behaviour is expected, but at least it think it should change. I'll attempt to fix it as described above and then close the issue at that point, even thou my Ruby skills = zero :-/ (and as far as i remember the plugin is written in ruby.) Jenkins / JENKINS-28973 naming autogenerated project does not postfix with branchname on first creation Change By: Thomas Blitz Resolution: Not A Defect Status: Resolved Reopened
[JIRA] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url It is acceptable to set the webhook url to something like http://jenkins.url/gitlab/build_now/seedproject? I've made a fast check, and apparently the plugin can handle such a url, so it should be hard to just trigger seedproject in that case. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ec2-plugin] (JENKINS-32379) integrate with the 'config file provider' plugin
Title: Message Title Jae Gangemi created an issue Jenkins / JENKINS-32379 integrate with the 'config file provider' plugin Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 10/Jan/16 4:59 PM Priority: Minor Reporter: Jae Gangemi it would be great if you could add support to allow managing init-script data via the config files provider plugin so a single script could be used across multiple instances, but updated only once. thanks!! Add Comment
[JIRA] [weblogic-deployer-plugin] (JENKINS-31413) intermittently Deployer failing with socket closed Exception.
Title: Message Title simba s commented on JENKINS-31413 Re: intermittently Deployer failing with socket closed Exception. yes Please. Thank you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-32371) Excessive wait times to clear build/node assocation after job completes
Title: Message Title Daniel Beck commented on JENKINS-32371 Re: Excessive wait times to clear build/node assocation after job completes Please provide a thread dump taken during this waiting time: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [update-sites-manager-plugin] (JENKINS-32376) Private certifacates doesn't work with server-based download (Jenkins >= 1.557)
Title: Message Title Daniel Beck commented on JENKINS-32376 Re: Private certifacates doesn't work with server-based download (Jenkins >= 1.557) To clarify, this also happens when specifying a certification with the custom update site? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Javier Palacios commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url Right. Was as not hard that you have a preliminar but working version on http://maven.jenkins-ci.org/content/repositories/snapshots/org/jenkins-ci/ruby-plugins/gitlab-hook/1.4.2-SNAPSHOT/ Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-29317) Trigger only autogenerated jobs, not all the jobs for given git url
Title: Message Title Vladimir Sitnikov commented on JENKINS-29317 Re: Trigger only autogenerated jobs, not all the jobs for given git url It is acceptable to set the webhook url to something like http://jenkins.url/gitlab/build_now/seedproject? I think so. However, in the long run "dumb configuration of webhook" + "smart configuration at jenkins side" might be better. so it should be hard to just trigger seedproject in that case. You mean "it should not be hard to trigger in that case", don't you? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Serg Pr updated an issue Jenkins / JENKINS-32186 bad links to bitbucket Change By: Serg Pr Issue Type: Bug Task Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation Then, scenario 2 hits a bug, which is fixed on release 1.4.1.1. The acceptance tests for template based creation performs these steps successfully Finds fallback template Does not create project for tag Creates project from template Does nothing for tags Builds a push to master branch and the second push uses the already created project, and does not create a new one. Anyway, I'll add an option to postfix the branch name even on template based creation, because it has sense and covers the case where the first push after configuring webhook is not for master branch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-24278) Node monitor for free inodes
Title: Message Title Oleg Nenashev commented on JENKINS-24278 Re: Node monitor for free inodes Yeah, inclusion into the core will require some debates. My Jenkins background says that "inodes" are critical for slave health, so personally I would +1 the inclusion. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gitlab-hook-plugin] (JENKINS-28973) naming autogenerated project does not postfix with branchname on first creation
Title: Message Title Javier Palacios commented on JENKINS-28973 Re: naming autogenerated project does not postfix with branchname on first creation And yes, I'm current developer of plugin. I don't usually use skype, but If your timezone is compatible with something like 20:00 GMT, we can arrange a chat. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-24278) Node monitor for free inodes
Title: Message Title Baptiste Mathus commented on JENKINS-24278 Re: Node monitor for free inodes Oleg Nenashev OK, thanks for your feedback. Gonna see to file a PR into core (actually didn't consider disk-usage-plugin because we for one uninstalled it some months ago after noticing it was a perf hog, and didn't investigate more, but maybe only a small issue that was fixed since, granted). At least that will let us know what others think about that into core. Because according to the current trend, the path would likely more to actually extract the existing classes from core than to add new ones . Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [weblogic-deployer-plugin] (JENKINS-31413) intermittently Deployer failing with socket closed Exception.
Title: Message Title Raphael CHAUMIER closed an issue as Not A Defect Jenkins / JENKINS-31413 intermittently Deployer failing with socket closed Exception. Change By: Raphael CHAUMIER Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [amazon-ecs-plugin] (JENKINS-31197) New jobs are not creating a new container
Title: Message Title Lee Webb commented on JENKINS-31197 Re: New jobs are not creating a new container I've got 3 different ECS task templates using a single cluster. These are used by about 20 jobs with the config set to allow for parallelisation if a job is already running. What I've seen is that the ECS cloud will spool up as many slave tasks as it can based on queued jobs before AWS starts responding back with RESOURCE:MEMORY etc. errors when attempting to create another slave task. My ECS cluster in AWS is setup on top of an autoscaling group, so the intent is to watch the job queue & the number of running builds to scale out / scale in by adjusting the autoscale desired_capacity number - the plugin won't do this by itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-23063) White spaces in a Project name of a job makes the Test Result Trend fail
Title: Message Title evernat resolved as Duplicate Jenkins / JENKINS-23063 White spaces in a Project name of a job makes the Test Result Trend fail Change By: evernat Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-32186 bad links to bitbucket Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [bitbucket-plugin] (JENKINS-32186) bad links to bitbucket
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-32186 bad links to bitbucket Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-23863) HTTP requests hang indefinitely after some time running
Title: Message Title evernat resolved as Not A Defect the server memory is full, it's normal that the server stops responding Jenkins / JENKINS-23863 HTTP requests hang indefinitely after some time running Change By: evernat Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-23456) I'm getting 23456!!!
Title: Message Title evernat resolved as Incomplete Yes, you can. Jenkins / JENKINS-23456 I'm getting 23456!!! Change By: evernat Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [azure-slave-plugin] (JENKINS-24665) "Open Issues" link on the Azure Slave Plugin wiki page is wrong
Title: Message Title suresh nallamilli resolved as Fixed I am seeing that JIRA component is "azure-slave-plugin". May be some one else changed it. Jenkins / JENKINS-24665 "Open Issues" link on the Azure Slave Plugin wiki page is wrong Change By: suresh nallamilli Status: Open Resolved Assignee: Martin Sawicki suresh nallamilli Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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
[JIRA] [azure-slave-plugin] (JENKINS-24665) "Open Issues" link on the Azure Slave Plugin wiki page is wrong
Title: Message Title suresh nallamilli closed an issue as Fixed Jenkins / JENKINS-24665 "Open Issues" link on the Azure Slave Plugin wiki page is wrong Change By: suresh nallamilli Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [azure-slave-plugin] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title suresh nallamilli assigned an issue to suresh nallamilli Jenkins / JENKINS-30014 Builds hang, Jenkins still browseable Change By: suresh nallamilli Assignee: suresh nallamilli Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [dependency-check-jenkins-plugin] (JENKINS-32327) Unable to abort running job during "Analyzing Dependencies" phase
Title: Message Title Steve Springett commented on JENKINS-32327 Re: Unable to abort running job during "Analyzing Dependencies" phase What OS and Jenkins version are you running? Try disabling the Maven Central analyzer from the Jenkins global configuration. DC Core might be getting stuck there. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
