date:20180502

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 [~pmilliken] [~ok2332] FYI I created a [PR#3415|https://github.com/jenkinsci/jenkins/pull/3415] to address your concern. Feel free to test / review it.Also filed a separate issue : [JENKINS-51064|https://issues.jenkins-ci.org/browse/JENKINS-51064]And a [PR#3416|https://github.com/jenkinsci/jenkins/pull/3416]for adding the direct "Dismiss" button in this monitor message.  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 [~pmilliken] [~ok2332] FYI I created a [PR#3415|https://github.com/jenkinsci/jenkins/pull/3415] to address your concern. Feel free to test / review it.Also filed a separate issue : [JENKINS-51064|https://issues.jenkins-ci.org/browse/JENKINS-51064] And a [PR#3416|https://github.com/jenkinsci/jenkins/pull/3416]for adding the direct "Dismiss" button in this monitor message.  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

2018-05-02 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Wadeck Follonier I wonder whether you could just consider rootUrlFromRequest for the admin monitor – if that's the same as is configured, it can't be too wrong. WDYT?  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

2018-05-02 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-31661  
 
 
  Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
Change By: 
 Daniel Beck  
 
 
Comment: 
 The Jenkins weekly release that contains the fix for this, 2.119, has references this issue in community feedback, and it's unclear why.*If you experience problems related to this change, please file a new issue describing those problems, and link to it.*  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

2018-05-02 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 The Jenkins weekly release that contains the fix for this, 2.119, has references this issue in community feedback, and it's unclear why. If you experience problems related to this change, please file a new issue describing those problems, and link to it.  
 

  
 
 
 
 

 
 
 

 
 
 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-30148) Allocate shorter workspace if it will be too long for reasonable use inside build

2018-05-02 Thread ogon...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-30148  
 
 
  Allocate shorter workspace if it will be too long for reasonable use inside build   
 

  
 
 
 
 

 
Change By: 
 Oliver Gondža  
 
 
Assignee: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 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-30148) Allocate shorter workspace if it will be too long for reasonable use inside build

2018-05-02 Thread ogon...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža commented on  JENKINS-30148  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allocate shorter workspace if it will be too long for reasonable use inside build   
 

  
 
 
 
 

 
 I am unassuming as I do not intend to work on this anytime soon...  
 

  
 
 
 
 

 
 
 

 
 
 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-51062) JEP-200 issue with plugin Gradle Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández updated  JENKINS-51062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-51066) pipeline-editor always commit to default jenkinsfile

2018-05-02 Thread zhaos...@shanghai-electric.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sam Zhao created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51066  
 
 
  pipeline-editor always commit to default jenkinsfile   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 screenshot1.png, screenshot2.png, screenshot3.png, screenshot4.png  
 
 
Components: 
 blueocean-pipeline-editor-plugin  
 
 
Created: 
 2018-05-02 10:25  
 
 
Environment: 
 Jenkins ver. 2.73.3  BlueOcean 1.5.0 - Core 2.73.3  
 
 
Labels: 
 jenkins blueocean-imported  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sam Zhao  
 

  
 
 
 
 

 
 Hi, When we use more than one Jenkinsfile in different jobs, you can see screenshot 1, pipeline scans the right 'Jenkinsfile-prd' for example(screenshot2). And when execute the pipeline it also use the right 'Jenkinsfile-prd'(screenshot3). But when use http:///blue/organizations/jenkins/pipeline-editor// to edit pipeline, it always shows the default Jenkinsfile and only can commit to default Jenkinsfile.(screenshot4). It seems /blue/organizations/jenkins/pipeline-editor/ always read the default Jenkinsfile and ignored the Build Configuration--Script Path. The difference between 2 Jenkinsfiles are environment: env in this example.

[JIRA] (JENKINS-51065) SHAREDSPACE_SCM_URL doesn't refresh when shared workspace url gets updated

2018-05-02 Thread domi...@zalewski.io (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dominik Zalewski created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51065  
 
 
  SHAREDSPACE_SCM_URL doesn't refresh when shared workspace url gets updated   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 shared-workspace-plugin  
 
 
Created: 
 2018-05-02 10:17  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Dominik Zalewski  
 

  
 
 
 
 

 
 When I update repository url under workspaces and run a job, ${SHAREDSPACE_SCM_URL} variable doesn't resolve to the new url. I need to configure the job and hit save then when I run it points to the updated scm url      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Paul Milliken Omar Kohl FYI I created a PR#3415 to address your concern. Feel free to test / review it. Also filed a separate issue : JENKINS-51064  
 

  
 
 
 
 

 
 
 

 
 
 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-51064) Lenient URL validator for Root URL

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51064  
 
 
  Lenient URL validator for Root URL   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Wadeck Follonier  
 
 
Components: 
 core  
 
 
Created: 
 2018-05-02 10:04  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Wadeck Follonier  
 

  
 
 
 
 

 
 After the JENKINS-31661 introduction, Paul Milliken and Omar Kohl reported troubles with the too strict validation. We need to be more lenient especially with the TLDs.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-51063) Multibranch pipeline does not handle correctly webhook of kind tag created

2018-05-02 Thread nfalc...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51063  
 
 
  Multibranch pipeline does not handle correctly webhook of kind tag created   
 

  
 
 
 
 

 
Change By: 
 Nikolas Falco  
 
 
Attachment: 
 newTagPayload.json  
 

  
 
 
 
 

 
 
 

 
 
 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted commented on  JENKINS-50993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
 Sam Van Oort could you shed some lights on 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted edited a comment on  JENKINS-50993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
 LogActionImpl does exist in workflow xml1) The log link is missing if called by  {color:red}runs?fullStages=true{color}&_=15252542918482)  The log link can be retrieved via individual rest api, such as /job/debug/job/stage_view_debug/ 9 7 /execution/node/15/wfapi/describe!Screen Shot 2018-05-02 at 3.06.03 PM.png!The xml is{code}more 15.xml1415org.jenkinsci.plugins.workflow.steps.EchoStep  1525244349821  UTF-8message  Sample Pipeline for Testtrue  {code}  
 

  
 
 
 
 

 
 
 

 
 
 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted edited a comment on  JENKINS-50993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
 LogActionImpl does exist in workflow xml1) The log link is missing  although LogActionImpl is in xml  if called by  {color:red}runs?fullStages=true{color}&_=1525254291848  2)  The log link can be retrieved via individual rest api, such as /job/debug/job/stage_view_debug/9/execution/node/15/wfapi/describe   !Screen Shot 2018-05-02 at 3.06.03 PM.png!The xml is{code}more 15.xml1415org.jenkinsci.plugins.workflow.steps.EchoStep  1525244349821  UTF-8message  Sample Pipeline for Testtrue  {code}   
 

  
 
 
 
 

 
 
 

 
 
 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-51063) Multibranch pipeline does not handle correctly webhook of kind tag created

2018-05-02 Thread nfalc...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51063  
 
 
  Multibranch pipeline does not handle correctly webhook of kind tag created   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 bitbucket-branch-source-plugin  
 
 
Created: 
 2018-05-02 09:47  
 
 
Environment: 
 Jenkins ver. 2.107.2  bitbucket-branch-source-plugin 2.2.11  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Nikolas Falco  
 

  
 
 
 
 

 
 When I create a tag on Bitbucket Cloud the webhook notify Jenkins for a new tag. But the jenkins plugin does not handle it has a SCM event of kind tag but as branch created event.   The PushHookProcessor should be changed (line 165) to check of which kind of event is the notification. 

 

if (change.isClosed()) {
	result.put(new BranchSCMHead(change.getOld().getName(), type), null);
} else {
	// created is true
	Reference newChange = change.getNew();
	SCMHead head = null;
	if ("tag".equals(newChange.getType())) {
		head = new BitbucketTagSCMHead(newChange.getName(), newChange.getDate().getTime(), type);
	} else {
		head = new BranchSCMHead(newChange.getName(), type);
	}
...
}
 

 It is also needed add date to the com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketPushEvent.Reference. I also suggest to configure the ObjectMapper in payload parser (JsonParser) to use the ISO8601DateFormat that comes with jackson instead the custom. Use a specific deserialiser for BitbucketCloudRepository.updatedOn where BB sends an invalid ISO8601 date format (6 decimal for milliseconds field instead 3 that cause date parse error

[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build

2018-05-02 Thread sorin.sbar...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sorin Sbarnea commented on  JENKINS-30148  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allocate shorter workspace if it will be too long for reasonable use inside build   
 

  
 
 
 
 

 
 Any change of having this fixed, ever, at least for normal pipelines? Here is one real life example:  /home/rhos-ci/jenkins/workspace/DFG-storage-cinder-20_director-rhel-virthost-3cont_2comp-ipv4-vxlan-netapp-nfs-external-ssbarnea With the mention that limiting the job name is impossible, there are tens of people creating jobs and no way to enforce a limit, in addition that an attempt to rename >1000 existing jobs would be an epic failure. The only thing where it may be possible to cut few characters is on jenkins slave HOME directory and subfolder, but other than this nope. Even so, changing this would be quite complex too as it would  involve lots of slaves type which are created by various people where almost for sure you will endup with some not using the shortened home directory workaround. Still, even if I manage to pick the minimum possible home directory, of "/j" it will clearly not be enough to make virtuaenvs working because job names will continue to be too long. **   
 

  
 
 
 
 

 
 
 

 
 
 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50993  
 
 
  Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
Change By: 
 Ted  
 
 
Comment: 
 per the code https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/AtomFlowNodeExt.java#L57I guess node.getAction may have caching 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Omar Kohl you're totally right, it was not the expected behavior concerning the TLD, I explicitely added the "_" case for internal hostname but not thought about the custom TLDs.  
 

  
 
 
 
 

 
 
 

 
 
 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-50961) Redirect link broken, double slash

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Sprinz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50961  
 
 
  Redirect link broken, double slash   
 

  
 
 
 
 

 
Change By: 
 Jan Sprinz  
 
 
Summary: 
 GitHub status redirect Redirect  link broken , double slash  
 

  
 
 
 
 

 
 
 

 
 
 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-50961) GitHub status redirect link broken

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Sprinz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50961  
 
 
  GitHub status redirect link broken   
 

  
 
 
 
 

 
Change By: 
 Jan Sprinz  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-50961) GitHub status redirect link broken

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Sprinz updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50961  
 
 
  GitHub status redirect link broken   
 

  
 
 
 
 

 
Change By: 
 Jan Sprinz  
 
 
Attachment: 
 Bildschirmfoto zu 2018-05-02 11-26-05.png  
 

  
 
 
 
 

 
 
 

 
 
 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-50961) GitHub status redirect link broken

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jan Sprinz commented on  JENKINS-50961  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub status redirect link broken   
 

  
 
 
 
 

 
 Turns out this can have significantly more severe effects, since it also affects the webhook-bot. See attached screenshot.   
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Kohl commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 OK I switched the corresponding administrative monitor off. You may want to consider being less strict. Why should it be a problem to use internal domains even though they are invalid TLDs? Just a thought...  
 

  
 
 
 
 

 
 
 

 
 
 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-47254) Support for building tags for Bitbucket Server/Cloud

2018-05-02 Thread nfalc...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nikolas Falco commented on  JENKINS-47254  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support for building tags for Bitbucket Server/Cloud   
 

  
 
 
 
 

 
 Jenkins does not handle notify of kind tag created because actually in the com.cloudbees.jenkins.plugins.bitbucket.hooks.PushHookProcessor Line 165 it create always a notify of kind branch. It should check if change.getNew().getType() is valued with branch or tag and create the appropriate SCMHead event (BitbucketTagSCMHead instead of BranchSCMHead)  
 

  
 
 
 
 

 
 
 

 
 
 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-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable

2018-05-02 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu updated  JENKINS-45817  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-45817  
 
 
  Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable   
 

  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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-51062) JEP-200 issue with plugin Gradle Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández commented on  JENKINS-51062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
 After analysing all the exceptions, the classes that seem to be affected are: 
 
hudson.plugins.gradle.BuildScanAction 
hudson.plugins.gradle.Gradle 
hudson.plugins.gradle.Gradle$DescriptorImpl 
hudson.plugins.gradle.GradleInstallation 
hudson.plugins.gradle.GradleInstallation$DescriptorImpl 
hudson.plugins.gradle.GradleInstaller 
 All of them seems to be fine since their non transient field are String, so probably the fix could be just adding those class to the whitelist (via hudson.remoting.ClassFilter file).  
 

  
 
 
 
 

 
 
 

 
 
 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-25829) Proxy configuration does not work

2018-05-02 Thread kab...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Viachaslau Kabak commented on  JENKINS-25829  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Proxy configuration does not work   
 

  
 
 
 
 

 
 Have no chance to test for now, sorry  
 

  
 
 
 
 

 
 
 

 
 
 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-51062) JEP-200 issue with plugin Gradle Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández started work on  JENKINS-51062  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-51062) JEP-200 issue with plugin Gradle Plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51062  
 
 
  JEP-200 issue with plugin Gradle Plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Francisco Fernández  
 
 
Components: 
 gradle-plugin  
 
 
Created: 
 2018-05-02 09:13  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Francisco Fernández  
 

  
 
 
 
 

 
 Executing the test suit for gradle-plugin against jenkins-core:2.107.2 to check compatibility, several of them are failing due to a Serialization exception. These errors seems to be related to JEP-200. As example, the following trace shows one of the exceptions:   

 

java.lang.RuntimeException: java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Project#builders for class hudson.model.FreeStyleProject
	at hudson.util.PersistedList._onModified(PersistedList.java:183)
	at hudson.util.PersistedList.add(PersistedList.java:72)
	at org.jvnet.hudson.test.JenkinsRule.configRoundtrip(JenkinsRule.java:1086)
	at hudson.plugins.gradle.GradlePluginIntegrationTest.Config roundtrip(GradlePluginIntegrationTest.groovy:180)
Caused by: java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.Project#builders for class hudson.model.FreeStyleProject
	at hudson.XmlFile.write(XmlFile.java:201)
	at hudson.model.AbstractItem.save(AbstractItem.java:483)
	at hudson.model.Job.save(Job.java:196)
	at hudson.model.AbstractProject.save(AbstractProject.java:289)
	at hudson.util.PersistedList.onModified(PersistedList.java:173)
	at hudson.util.PersistedList._onModified(PersistedList.java:181)
	... 3 more
Caused by: java.lang.RuntimeException: Failed to serialize hudson.model.Project#builders

[JIRA] (JENKINS-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs

2018-05-02 Thread jackie.x...@ebaotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jackie Xiao commented on  JENKINS-39615  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs   
 

  
 
 
 
 

 
 Also facing this issue, we have lots of microservice CI/CD jobs configured, which depend on the shared library, any change made to the shared lib will trigger all downstream jobs. Looking forward to the fix.  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Omar Kohl in your case the problem is the .intern that is not standard and so is not considered as valid by the apache library we use to validate the URL. The trailing slash is not a problem. FYI it is added if not present in the form.  
 

  
 
 
 
 

 
 
 

 
 
 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-45817) Branch selector has a down-arrow which looks like a context-menu selector but isn't clickable

2018-05-02 Thread npa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolae Pascu started work on  JENKINS-45817  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Nicolae Pascu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wadeck Follonier edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 [~ok2332] in your case the problem is the {{.intern}} that is not standard and so is not considered as valid by the apache library we use to validate the URL.The trailing slash is not a problem. FYI it is added if not present in the form. So for the moment, I think the best is just to follow the above workaround steps to disable the monitor.  
 

  
 
 
 
 

 
 
 

 
 
 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-51061) No commits are discovered by Jenkins

2018-05-02 Thread cvieri.l...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleksii Molchanov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51061  
 
 
  No commits are discovered by Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Mark Waite  
 
 
Components: 
 git-plugin  
 
 
Created: 
 2018-05-02 08:55  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oleksii Molchanov  
 

  
 
 
 
 

 
 No commits are visible under multibranch pipeline run, thus affectedFiles list is empty, when using "git commit --amend" and "git push --force" 

 

checkout([
 $class: 'GitSCM',
 branches: scm.branches,
 extensions: scm.extensions + [[$class: 'LocalBranch'], [$class: 'CleanCheckout']],
 userRemoteConfigs: scm.userRemoteConfigs,
 ]) 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Kohl edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Same issue here. It is constantly showing that message. The only  _unusual_   thing I can think of is that the domain is not public but it is configured in an internal DNS Server that is properly included in */etc/resolv.conf* on the Jenkins server. From the command-line of said server it is no problem to resolve the domain.The URL is: [https://jenkins.XXX.intern/|https://jenkins.xxx.intern/] where XXX is just ASCII letters. No special characters.I tried removing the trailing slash (since you have no testcase with a trailing slash) but it keeps getting added again and therefore makes no difference. <
 /td> 
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Kohl edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Same issue here. It is constantly showing that message. The only thing I can think of is that the domain is not public but it is configured in an internal DNS Server that is properly included in */etc/resolv.conf* on the Jenkins server. From the command-line of said server it is no problem to resolve the domain.The URL is: [https://jenkins.XXX.intern/|https://jenkins.xxx.intern/] where XXX is just ASCII letters. No special characters. I tried removing the trailing slash (since you have no testcase with a trailing slash) but it keeps getting added again and therefore makes no difference.  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Kohl edited a comment on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Same issue here. It is constantly showing that message. The only thing I can think of is that the domain is not public but it is configured in an internal DNS Server that is properly included in */etc/resolv.conf* on the Jenkins server. From the command-line of said server it is no problem to resolve the domain.The URL is:  [  https://jenkins.XXX.intern/ |https://jenkins.xxx.intern/] where XXX is just ASCII letters. No special characters.  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title


 
 
 
 

 
 
 

 
   
 Omar Kohl commented on  JENKINS-31661  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins.rootUrl too often unset or incorrect   
 

  
 
 
 
 

 
 Same issue here. It is constantly showing that message. The only thing I can think of is that the domain is not public but it is configured in an internal DNS Server that is properly included in /etc/resolv.conf on the Jenkins server. From the command-line of said server it is no problem to resolve the domain. The URL is: https://jenkins.XXX.intern/  
 

  
 
 
 
 

 
 
 

 
 
 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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title

Wadeck Follonier edited a comment on JENKINS-31661

Re: Jenkins.rootUrl too often unset or incorrect

[~pmilliken] Thank you for your comment.You can see some examples of expected behavior in [test|https://github.com/jenkinsci/jenkins/pull/3082/files#diff-9d74f3aa63b04fe0467f0dfcf333446eR13].If you can provide the URL you are using (if it's not confidential, etc.) we can perhaps detect if it's a bug in our URL validation. We use the standard validator and even add the "_" in the authorized list of characters. Perhaps you are just using a character that works but is not standard in your URL.If you want to hide the warning, you can dismiss them in the configuration. For that reason there is not need (at least until now) to provide a way to validate a data that seems incorrect for the admin monitor. To disable an administrative monitor, # you need to go (as admin) in " Manage Jenkins " # " Configure System " # inside " Administratrive monitors configuration " section # Click click on [ Administrative monitors... ] on the right # Uncheck uncheck the one you want to disable and then # finally save (or apply).

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-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title

Wadeck Follonier edited a comment on JENKINS-31661

Re: Jenkins.rootUrl too often unset or incorrect

[~pmilliken] Thank you for your comment.You can see some examples of expected behavior in [test ]( | https://github.com/jenkinsci/jenkins/pull/3082/files#diff-9d74f3aa63b04fe0467f0dfcf333446eR13 ) ] .If you can provide the URL you are using (if it's not confidential, etc.) we can perhaps detect if it's a bug in our URL validation. We use the standard validator and even add the "_" in the authorized list of characters. Perhaps you are just using a character that works but is not standard in your URL.If you want to hide the warning, you can dismiss them in the configuration. For that reason there is not need (at least until now) to provide a way to validate a data that seems incorrect for the admin monitor. To disable an administrative monitor, you need to go (as admin) in Manage Jenkins > Configure System > Administratrive monitors configuration > Click on Administrative monitors... > Uncheck the one you want to disable and then save (or apply).

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title

Wadeck Follonier edited a comment on JENKINS-31661

Re: Jenkins.rootUrl too often unset or incorrect

[~pmilliken] Thank you for your comment. You can see some examples of expected behavior in [test|https://github.com/jenkinsci/jenkins/pull/3082/files#diff-9d74f3aa63b04fe0467f0dfcf333446eR13].If you can provide the URL you are using (if it's not confidential, etc.) we can perhaps detect if it's a bug in our URL validation. We use the standard validator and even add the "_" in the authorized list of characters. Perhaps you are just using a character that works but is not standard in your URL.If you want to hide the warning, you can dismiss them in the configuration. For that reason there is not need (at least until now) to provide a way to validate a data that seems incorrect for the admin monitor.To disable an administrative monitor, # you need to go (as admin) in Manage Jenkins > # Configure System > # Administratrive monitors configuration > # Click on Administrative monitors... > # Uncheck the one you want to disable and then save (or apply).

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect

Title: Message Title

Wadeck Follonier commented on JENKINS-31661

Re: Jenkins.rootUrl too often unset or incorrect

Paul Milliken Thank you for your comment. You can see some examples of expected behavior in [test](https://github.com/jenkinsci/jenkins/pull/3082/files#diff-9d74f3aa63b04fe0467f0dfcf333446eR13). If you can provide the URL you are using (if it's not confidential, etc.) we can perhaps detect if it's a bug in our URL validation. We use the standard validator and even add the "_" in the authorized list of characters. Perhaps you are just using a character that works but is not standard in your URL. If you want to hide the warning, you can dismiss them in the configuration. For that reason there is not need (at least until now) to provide a way to validate a data that seems incorrect for the admin monitor. To disable an administrative monitor, you need to go (as admin) in Manage Jenkins > Configure System > Administratrive monitors configuration > Click on Administrative monitors... > Uncheck the one you want to disable and then save (or apply).

Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1

2018-05-02 Thread aiman.als...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Aiman Alsari commented on  JENKINS-47501  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: 2 pods are started instead of 1 after update to version 1.1   
 

  
 
 
 
 

 
 I found that someone else has also seen this issue. See Yuan Yao's comment on JENKINS-44042  
 

  
 
 
 
 

 
 
 

 
 
 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted commented on  JENKINS-50993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
 per the code  https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/AtomFlowNodeExt.java#L57 I guess node.getAction may have caching 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ted commented on  JENKINS-50993  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled   
 

  
 
 
 
 

 
 log link is missing although LogActionImpl is in xml  The xml is 

 

more 15.xml

"workflow-support@2.18">
  "cps.n.StepAtomNode" plugin="workflow-cps@2.45">

  14

15
org.jenkinsci.plugins.workflow.steps.EchoStep
  
  
"workflow-api@2.25">
  1525244349821


  UTF-8

"workflow-cps@2.45">
  "linked-hash-map">

  message
  Sample Pipeline for Test

  
  true

  

 

  
 

  
 
 
 
 

 
 
 

 
 
 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-50993) Pipeline-Stage-View Plugin is unable to show stage logs when Splunk Plugin for Jenkins is Enabled