[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title Stefan Cordes commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs The above workaround is valid for existing branches in a multibranch project. For new branches the Bitbucket trigger still fails. For that reason I investigated a little bit and found out that the Bitbucket trigger is just checking for instanceof BitBucketTrigger but the MultiBranch Pipeline is not a BitBucketTrigger but a SCMSourceOwner So I modified the BitbucketJobProbe to consider jenkins.scm.api.SCMSourceOwner: https://github.com/jenkinsci/bitbucket-plugin/pull/68 (With that pull request the above "existing branch" Workaround: [$class: 'com.cloudbees.jenkins.plugins.BitBucketTrigger'] (or ,bitbucketPush()) can be removed again) Can someone merge it, please? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174627.1474550199000.2788.1583748420980%40Atlassian.JIRA.
[JIRA] (JENKINS-61361) Replace "accountId" workaround when jira-rest-java-client is updated
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-61361 Replace "accountId" workaround when jira-rest-java-client is updated Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2020-03-06 09:12 Priority: Minor Reporter: Stefan Cordes With JENKINS-56987 (Pull Request https://github.com/jenkinsci/jira-plugin/pull/213 ) one line in hudson.plugins.jira.JiraRestService.createIssue(String, String, String, Iterable, String, Long, Long) needed to use a workaround to set "accountId" instead of "name". When the GDPR changes are fully merged in jira-rest-java-client (probably version 5.2.2) https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/104/change-field-name-from-name-to-accountid the workaround can be changed back to builder.setAssigneeName(assignee) (or builder.setAssigneeAccountId(assignee) depending on the provided solution)
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Stefan Cordes commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON This is caused by Jira-Cloud implementing GDPR compliance on 14.Feb.2020 in the Cloud API. The jira-rest-java-client version 5.2.0 (which is reflecting that change) was released last friday (one week later ) For the jira-plugin two pull request are handling that moving to 5.1.6: https://github.com/jenkinsci/jira-plugin/pull/212 and then to 5.2.0: https://github.com/jenkinsci/jira-plugin/pull/213 Similar solution should be feasible here for jira-trigger-plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201336.1566200967000.5860.1582623360597%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error As JENKINS-61184 was marked as duplicate of JENKINS-58987 I placed the comment there. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.5869.1582623360702%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Stefan Cordes commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON JsonParseUtil is released in version 5.2.0, see https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid#comment-137009716 Kamil Cichy commented on pull request #93: JRJC-240: Added support for accountId. Hello everyone, First of all I’m sorry it took so long to merge this PR. This is because this plugin is not supported. It means nobody is watching the PR queue and we don’t have any time budgeted to work on this. You should really thank @Andy Heinzer for nudging us to merge it I reviewed the code to ensure it was backwards-compatible. Then I had to do some extra work to fix the CI for this plugin (it’s been broken since 8.4.0). Only then I was able to release it (the second attempt was successful). I’m only writing this to justify our inability to support this plugin properly. What seems to be a single “merge” click was in fact a couple of hours of work. Anyway, this PR is merged, plugin version 5.2.0 has been released. Hopefully better late than ever. Kamil Jira Server and DC developer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error 5.2.0 is release, see https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid#comment-137009716 Kamil Cichy commented on pull request #93: JRJC-240: Added support for accountId. Hello everyone, First of all I’m sorry it took so long to merge this PR. This is because this plugin is not supported. It means nobody is watching the PR queue and we don’t have any time budgeted to work on this. You should really thank @Andy Heinzer for nudging us to merge it I reviewed the code to ensure it was backwards-compatible. Then I had to do some extra work to fix the CI for this plugin (it’s been broken since 8.4.0). Only then I was able to release it (the second attempt was successful). I’m only writing this to justify our inability to support this plugin properly. What seems to be a single “merge” click was in fact a couple of hours of work. Anyway, this PR is merged, plugin version 5.2.0 has been released. Hopefully better late than ever. Kamil Jira Server and DC developer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Stefan Cordes edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
{quote}Merged pull requestMerged in master (pull request #93)78059d9Jakub Sławiński18 minutes ago{quote}[https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93] Due to "JRJC-240: Bump plugin version to 5.2.0-SNAPSHOT" it looks like next version will be 5.2.0 and not 5.1.7.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.4178.1582282440420%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Merged pull request Merged in master (pull request #93) 78059d9 Jakub Sławiński 18 minutes ago https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.4150.1582282140337%40Atlassian.JIRA.
[JIRA] (JENKINS-61175) Provide different JiraIssueUpdater for cloud and server
Title: Message Title
Stefan Cordes updated an issue
Jenkins / JENKINS-61175
Provide different JiraIssueUpdater for cloud and server
Change By:
Stefan Cordes
According to Ben_Kelley from ATLASSIAN TEAM the currently used libraryjira-rest-java-client is for server-edition of Jira only,see [https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944]{quote} Ben_Kelley ATLASSIAN TEAM TuesdayPlease note the section under "Compatibility with Jira" for JRJC on [ https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview ] The Jira REST Java Client works with Jira Server, but not with Jira Cloud.{quote} When communicating with the cloud edition a self-generated (java) client should be used:[https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133] As the jenkins jira-plugin should work with cloud edition +and+ onpremise server edition of Jira I guess there should be a "generic api" above of the [https://bitbucket.org/atlassian/jira-rest-java-client] and the self-generatedencapsulating the core-jira-functions necessary for jira-pluginto be sure all functions provided by jira-plugin work on both. Current APIs:Server Platform:https://docs.atlassian.com/software/jira/docs/api/REST/8.7.1/Cloud Platform: (v3 is already available as beta)https://developer.atlassian.com/cloud/jira/platform/rest/v2/
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61175) Provide different JiraIssueUpdater for cloud and server
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-61175 Provide different JiraIssueUpdater for cloud and server Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 2020-02-21 09:49 Priority: Minor Reporter: Stefan Cordes According to Ben_Kelley from ATLASSIAN TEAM the currently used library jira-rest-java-client is for server-edition of Jira only, see https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944 Ben_Kelley ATLASSIAN TEAM Tuesday Please note the section under "Compatibility with Jira" for JRJC on https://ecosystem.atlassian.net/wiki/spaces/JRJC/overview The Jira REST Java Client works with Jira Server, but not with Jira Cloud. When communicating with the cloud edition a self-generated (java) client should be used: https://community.atlassian.com/t5/Jira-articles/Generating-a-REST-client-for-Jira-Cloud/ba-p/1307133 As the jenkins jira-plugin should work with cloud edition and onpremise server edition of Jira I guess there should be a "generic api" above of the https://bitbucket.org/atlassian/jira-rest-java-client and the self-generated encapsulating the core-jira-functions necessary for jira-plugin to be sure all functions provided by jira-plugin work on both.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Stefan Cordes edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
Hi,looks like the "jira-rest-java-client" will be prepared for "accountId": [ JRJC-240: Added support for accountId.| https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93 ] "JRJC-240: Added support for accountId." But that still needs to be merged (will probably a {noformat} com.atlassian.jira jira-rest-java-client-api 5.1.7{noformat}but in comparison to the 5.0.4 version there are some more changes:(e.g. import static com.atlassian.util.concurrent.Promises where groupId changed from com.atlassian.util.concurrent to io.atlassian.util.concurrent and dependency is no longer available transitive)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.3507.1582196220542%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Stefan Cordes commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Hi, looks like the "jira-rest-java-client" will be prepared for "accountId": [https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93 ] "JRJC-240: Added support for accountId." But that still needs to be merged (will probably a com.atlassian.jira jira-rest-java-client-api 5.1.7 but in comparison to the 5.0.4 version there are some more changes: (e.g. import static com.atlassian.util.concurrent.Promises where groupId changed from com.atlassian.util.concurrent to io.atlassian.util.concurrent and dependency is no longer available transitive) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194307.1537972591000.3493.1582196160370%40Atlassian.JIRA.
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title
Stefan Cordes commented on JENKINS-38447
Re: Bitbucket hooks don't work for Pipeline jobs
Cesar Tron-Lozai : With
pipelineTriggers([
// build at least build onetime a month
// MINUTE HOUR DOM MONTH DOW
// see https://jenkins.io/doc/book/pipeline/syntax/#triggers
// # Build at least once a month
cron('H H(10-17) H * 1-5')
// for test every 5 minutes
//cron('*/5 * * * *')
,
// poll scm nightly to ensure no push events were lost.
pollSCM('H H(3-7) * * *')
,
// https://issues.jenkins-ci.org/browse/JENKINS-38447?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel=true
[$class: 'com.cloudbees.jenkins.plugins.BitBucketTrigger']
,
snapshotDependencies()
])
it worked for me when using $JENKINS_HOME/bitbucket-hook/ when
https bitbucket URL and not ssh
git and not bitbucket-source in "Project Repository"
(reason: see com.cloudbees.jenkins.plugins.BitbucketJobProbe.match(..))
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title Stefan Cordes updated an issue Jenkins / JENKINS-38447 Bitbucket hooks don't work for Pipeline jobs Change By: Stefan Cordes Attachment: branch-sources-https-and-pure-git.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174627.1474550199000.8894.1574954583189%40Atlassian.JIRA.
[JIRA] (JENKINS-44082) jiraGetVersion don't know id
Title: Message Title Stefan Cordes reopened an issue Link to example https://github.com/jenkinsci/jira-steps-plugin/issues/8 is broken (404). Please add "how it works" here. Jenkins / JENKINS-44082 jiraGetVersion don't know id Change By: Stefan Cordes Resolution: Not A Defect Status: Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181623.1493991687000.11757.1561739160326%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Stefan Cordes commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty Correct. Taking a look into WorkflowJob.java shows that it is kind of Workspace-Lock. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35359) Limit concurrent builds for 1 MultiBranch project
Title: Message Title Stefan Cordes commented on JENKINS-35359 Re: Limit concurrent builds for 1 MultiBranch project Maybe https://wiki.jenkins-ci.org/display/JENKINS/Lockable+Resources+Plugin helps workarounding the issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35359) Limit concurrent builds for 1 MultiBranch project
Title: Message Title Stefan Cordes commented on JENKINS-35359 Re: Limit concurrent builds for 1 MultiBranch project This is not a duplicate of JENKINS-34547 , see https://issues.jenkins-ci.org/browse/JENKINS-34547?focusedCommentId=291934=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-291934 (here it requested to have limit all branches of one multibranch project build one by one). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34547) Make WorkflowJob.concurrentBuild into a JobProperty
Title: Message Title Stefan Cordes commented on JENKINS-34547 Re: Make WorkflowJob.concurrentBuild into a JobProperty Moving properties ([ buildDiscarder(logRotator(numToKeepStr: '5')) , disableConcurrentBuilds() ]); to the very first line does not hinder 2 feature branches to build in parallel (as reported in JENKINS-35359) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36342) "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION
Title: Message Title Stefan Cordes commented on JENKINS-36342 Re: "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION Duplicate is ok. Hopefully DEFAULT_RELEASE_VERSION_ENVVAR is added to safeParams as well in JENKINS-35261 ( https://github.com/jenkinsci/m2release-plugin/pull/29/commits/9ae40671030ac7ffa495cea1208ff62be71a4bd9 ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36342) "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION
Title: Message Title Stefan Cordes commented on JENKINS-36342 Re: "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION Workaround should be add `-Dhudson.model.ParametersAction.safeParameters=MVN_RELEASE_VERSION,MVN_DEV_VERSION,MVN_ISDRYRUN` to the variable `JENKINS_JAVA_OPTIONS` in config file /etc/sysconfig/jenkins (see https://groups.google.com/forum/#!topic/jenkinsci-users/O2ccSWhKhpY ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36342) "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION
Title: Message Title Stefan Cordes updated an issue Jenkins / JENKINS-36342 "Editable Email Notification" does not resolve $MVN_RELEASE_VERSION Change By: Stefan Cordes Summary: " Delete Editable Email Notification" does not resolve $MVN_RELEASE_VERSION Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36342) "Delete Editable Email Notification" does not resolve $MVN_RELEASE_VERSION
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-36342 "Delete Editable Email Notification" does not resolve $MVN_RELEASE_VERSION Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2016/Jun/30 6:53 AM Priority: Minor Reporter: Stefan Cordes We have configured A: Request Deployment in SBM: $MVN_RELEASE_VERSION ($DEFAULT_SUBJECT) and before Jenkins 1.651.3 that resolved to the version number we specified in "Release" but now it just shows: A: Request Deployment in SBM: $MVN_RELEASE_VERSION (buyos-2016.6 - Build # 18 - Fixed!) This probably is caused by SECURITY-170 Add
[JIRA] [maven-plugin] (JENKINS-31966) False positive JDK5 detection during maven startup
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-31966 False positive JDK5 detection during maven startup Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 08/Dec/15 7:04 PM Environment: Windows Jenkins ver. 1.625.2 Priority: Major Reporter: Stefan Cordes With JENKINS-18403 additional to UnsupportedVersionException a SocketException was caught to detect "JDK5". Unfortunately the original cause is never logged. Since 1.625.2 we have 2 JDKs 1.6 which say "JDK5": ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to C:\swd\java\ibm_jdk1.6.0_sr8_fp1 and ERROR: JENKINS-18403 JDK 5 not supported to run Maven; retrying with slave Java and setting
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-30810) buildWithParamteres is used when '"actions":[{},{},{}]' is returned
Title: Message Title
Stefan Cordes created an issue
Jenkins / JENKINS-30810
buildWithParamteres is used when '"actions":[{},{},{}]' is returned
Issue Type:
Bug
Assignee:
Maurice W.
Components:
parameterized-remote-trigger-plugin
Created:
06/Oct/15 12:17 PM
Environment:
Jenkins ver. 1.609.3 2.2.2
Priority:
Major
Reporter:
Stefan Cordes
Our Remote Target Job answers http://test.jenkins.retail-sc.com//job/remote-trigger-test-target/api/json
{"actions":[{},{},{}],"description":"Triggered \"remotely\" by [{},{}],"queueItem":null,"concurrentBuild":false,"downstreamProjects":[],"scm":{},"upstreamProjects":[]}
which makes https://github.com/jenkinsci/parameterized-remote-trigger-plugin/commit/d544e329dc27fdf700c5f23191077b4a7074a4d9 decide to be parametrized:
if(response.getJSONArray("actions").size() >= 1) { isParameterized = true; }
Like the perform method it needs to be checked if there are parameters inside of the action: if (!action.has("parameters")) continue;
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-30571) Add support for https
Title: Message Title
Stefan Cordes created an issue
Jenkins / JENKINS-30571
Add support for https
Issue Type:
Bug
Assignee:
Maurice W.
Components:
parameterized-remote-trigger-plugin
Created:
21/Sep/15 2:39 PM
Priority:
Minor
Reporter:
Stefan Cordes
Allow setting https host for trigger server. Currently connection = (HttpURLConnection) buildUrl.openConnection(); in RemoteBuildConfiguration will get a classcastException.
(Checking with our Jenkins ver. 1.609.1 setting https://test.jenkins.retail-sc.com/ as "Remote address and port" fails with {{java.net.MalformedURLException: no protocol: https%3A%2F%2Ftest.jenkins.retail-sc.com%2F%2Fjob%2Ftest-1-run%2Fapi%2Fjson at java.net.URL.(URL.java:585) at java.net.URL.(URL.java:482) at java.net.URL.(URL.java:431) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.sendHTTPCall(RemoteBuildConfiguration.java:699) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.sendHTTPCall(RemoteBuildConfiguration.java:672) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.isRemoteJobParameterized(RemoteBuildConfiguration.java:916) at org.jenkinsci.plugins.ParameterizedRemoteTrigger.RemoteBuildConfiguration.perform(RemoteBuildConfiguration.java:482) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at
[JIRA] [jira-plugin] (JENKINS-25015) RemoteValidationException when using "Mark JIRA Version as Released"
Title: Message Title Stefan Cordes commented on JENKINS-25015 Re: RemoteValidationException when using "Mark JIRA Version as Released" Mark version as Release works now with Jira Plugin 2.0 and Jenkins 1.609.1 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] [jira-plugin] (JENKINS-25015) RemoteValidationException when using Mark JIRA Version as Released
Title: Message Title Stefan Cordes commented on JENKINS-25015 Re: RemoteValidationException when using Mark JIRA Version as Released When receiving Es konnte kein Projekt mit Schlssel 'MAV' gefunden werden. Cannot find Jira Project MAV you should check the authorization of the User you specified in Jenkins. (For testing add the user to all groups in your MAV-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] [junit-plugin] (JENKINS-28901) Trigger Exceptions are missing in JUnit Report
Title: Message Title
Stefan Cordes created an issue
Jenkins / JENKINS-28901
Trigger Exceptions are missing in JUnit Report
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Stacktrace-junit-result-page.png
Components:
junit-plugin
Created:
15/Jun/15 8:57 AM
Environment:
Windows Server, Jenkins ver. 1.580.3, JUnit Plugin 1.5
Priority:
Minor
Reporter:
Stefan Cordes
In case a class under test throws an Exception where a trigger is included, the trigger is not shown in the test result error page.
A Junit Test:
public class StacktraceTest { @Test public void testSameTriggerClass() { throw new IllegalArgumentException(Root, new IllegalArgumentException(Expected Trigger)); }
}
results in
Error Message
Root Stacktrace
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-27249) Quiet period is not considered when triggering remotely
Title: Message Title Stefan Cordes commented on JENKINS-27249 Re: Quiet period is not considered when triggering remotely Thank you, Daniel. Remove the line this.addToQueryString(delay=0); will fix this. 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-28415) REST API does not consider QuitePeriod
Title: Message Title Stefan Cordes created an issue Jenkins / JENKINS-28415 REST API does not consider QuitePeriod Issue Type: Bug Assignee: Unassigned Components: core Created: 15/May/15 7:20 AM Environment: Windows 2000 Server Jenkins 1.580.3 Priority: Minor Reporter: Stefan Cordes When a REST API call to build a project comes in the QuitePeriod is ignored. Quite Period should not be ignored. (Alternatively add a new paramter to the REST API to considerQuitePeriod=true or something else). Related to https://issues.jenkins-ci.org/browse/JENKINS-27249 Add Comment
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-27249) Quite Period is not considered when triggering remotely
Title: Message Title Stefan Cordes commented on JENKINS-27249 Re: Quite Period is not considered when triggering remotely Created Core issue: https://issues.jenkins-ci.org/browse/JENKINS-28415 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] [remoting] (JENKINS-27249) Quite Period is not considered when triggering remotely
Stefan Cordes created JENKINS-27249 Quite Period is not considered when triggering remotely Issue Type: Bug Assignee: Unassigned Components: remoting Created: 04/Mar/15 9:53 PM Description: 2 Jenkins Servers: build and integrate integrate has a deploy job with a "Quiet period" of 1800 (seconds) build triggers via "Parameterized Remote Trigger Plugin" Verison 2.1.3 with "Trigger a remote parameterized job" that job. The deploy job starts immediately. Expected is that the deploy job on integrate is queued and waits for 30 minutes. Seems to be that "Trigger builds remotely (e.g., from scripts)" with "Authentication Token" akts like pressing on the "Build" link. Should be like other build triggers. Environment: Windows 2000 Server Jenkins 1.580.3 Project: Jenkins Labels: jenkins Priority: Minor Reporter: Stefan Cordes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Stefan Cordes commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Seems to be fixed with Jenkins ver. 1.580.3 (and Maven 3.2.3) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Stefan Cordes edited a comment on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Can this be fixed in https://wiki.jenkins-ci.org/display/JENKINS/Task+Scanner+Plugin ? When switching off hudson.plugins.tasks.TasksReporter plugin="tasks@4.40" we no longer receive: 2014-09-17T13:26:10.115 [INFO] Building xx-jenkins-test-ejb 2014.3.1-15-SNAPSHOT 2014-09-17T13:26:10.117 [INFO] 2014-09-17T13:26:10.236 [INFO] 2014-09-17T13:26:10.236 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ xx-jenkins-test-ejb --- [TASKS] Scanning folder 'D:\jenkins-TEST-Slave1\workspace\xx-jenkins-test\xx\xx-jenkins-test\xx-jenkins-test-ejb' for files matching the pattern '**/*.java, **/*.xml' - excludes: [TASKS] Found 9 files to scan for tasks Found 0 open tasks. java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at $Proxy4.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:206) at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:325) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:316) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:600) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:315) at java.util.concurrent.FutureTask.run(FutureTask.java:150) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:898) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:920) at
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
edited a comment on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
{{ at hudson.model.Run.delete(Run.java:1432)}}
{{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}}
{{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}}
{{ at hudson.model.Job.logRotate(Job.java:437)}}
{{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}}
{{ at hudson.model.Run.execute(Run.java:1728)}}
{{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}}
{{ at hudson.model.ResourceController.execute(ResourceController.java:88)}}
{{ at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching jobs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
commented on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
{{Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
at hudson.model.Run.delete(Run.java:1432)
at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)
at hudson.tasks.LogRotator.perform(LogRotator.java:124)
at hudson.model.Job.logRotate(Job.java:437)
at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)
at hudson.model.Run.execute(Run.java:1728)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching jobs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Stefan Cordes
edited a comment on JENKINS-17508
The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.
Got an
Jan 28, 2014 9:03:44 AM hudson.model.Run execute
SEVERE: Failed to rotate log
java.io.IOException: e:\jenkins\jobs\.\modules\com$\builds\2013-10-23_11-57-46 looks to have already been deleted
{{ at hudson.model.Run.delete(Run.java:1432)}}
{{ at hudson.maven.MavenModuleSetBuild.delete(MavenModuleSetBuild.java:430)}}
{{ at hudson.tasks.LogRotator.perform(LogRotator.java:124)}}
{{ at hudson.model.Job.logRotate(Job.java:437)}}
{{ at hudson.maven.MavenModuleSet.logRotate(MavenModuleSet.java:840)}}
{{ at hudson.model.Run.execute(Run.java:1728)}}
{{ at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519)}}
{{ at hudson.model.ResourceController.execute(ResourceController.java:88)}}
{{ at hudson.model.Executor.run(Executor.java:246)}}
with Jenkins ver. 1.532.1.
(Mentioned directory 2013-10-23_11-57-46 is not existing on file system).
LogRotator should continue deleting all other matching jobs.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
