from:"pa...@batanov.me $JIRA$"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov assigned an issue to Pavel Batanov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36349  
 
 
  Multiple jobs without distinct matrices do not update Bitbucket Server correctly   
 

  
 
 
 
 

 
Change By: 
 Pavel Batanov  
 
 
Assignee: 
 Pavel Batanov  
 

  
 
 
 
 

 
 
 

 
 
 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-36349) Multiple jobs without distinct matrices do not update Bitbucket Server correctly

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-36349  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Multiple jobs without distinct matrices do not update Bitbucket Server correctly   
 

  
 
 
 
 

 
 Looks like your job keys are overlapping. Try to configure unique keys for jobs using custom configuration of post-build test. It allows to 
 
prepend parent's job key 
override the key itself (do not use the job name as key) 
add build number to job key (to track different builds on the same commit) 
  
 

  
 
 
 
 

 
 
 

 
 
 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-39347) Notify Stash plugin problems after update

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-39347  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Notify Stash plugin problems after update   
 

  
 
 
 
 

 
 Which version of plugin, jenkisn and stash\bitbucket do you use?  
 

  
 
 
 
 

 
 
 

 
 
 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-32324) Let stashnotifier plugin be able to resolve a url of scm which contains jenkins global property.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-32324  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Let stashnotifier plugin be able to resolve a url of scm which contains jenkins global property.   
 

  
 
 
 
 

 
 Created a GH clone to track it.  
 

  
 
 
 
 

 
 
 

 
 
 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-32817) stashnotifier-plugin credentials are broken

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-32817  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: stashnotifier-plugin credentials are broken   
 

  
 
 
 
 

 
 If it still relevant, feel free to report this on GH or comment here We fixed similar issues some time ago https://github.com/jenkinsci/stashnotifier-plugin/issues/86 https://github.com/jenkinsci/stashnotifier-plugin/pull/98  
 

  
 
 
 
 

 
 
 

 
 
 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-35551) Upgrade to Credentials 2.1.0+ API for populating credentials drop-down

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-35551  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Upgrade to Credentials 2.1.0+ API for populating credentials drop-down   
 

  
 
 
 
 

 
 Jenkins2, hit LTS, so we can do it, thank you  
 

  
 
 
 
 

 
 
 

 
 
 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-36346) StashNotifier plugin may hang forever if Stash server does not resond properly

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PR was accepted for the next release  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36346  
 
 
  StashNotifier plugin may hang forever if Stash server does not resond properly   
 

  
 
 
 
 

 
Change By: 
 Pavel Batanov  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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

[JIRA] (JENKINS-37262) Notify Stash does not work with ssh keys

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37262  
 
 
  Notify Stash does not work with ssh keys   
 

  
 
 
 
 

 
Change By: 
 Pavel Batanov  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Pavel Batanov  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 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-37262) Notify Stash does not work with ssh keys

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-37262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Notify Stash does not work with ssh keys   
 

  
 
 
 
 

 
 Sorry, I've not received this bug as was not auto-assigned and I did not check this tracker frequently (issues are mostly tracked on GH). The problem with SSH keys or other authentication mechanisms is that plugin uses REST API to communcate with bitbucket server, thus it uses login\password only. https://github.com/jenkinsci/stashnotifier-plugin/issues/45  
 

  
 
 
 
 

 
 
 

 
 
 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-37262) Notify Stash does not work with ssh keys

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov edited a comment on  JENKINS-37262  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Notify Stash does not work with ssh keys   
 

  
 
 
 
 

 
 Sorry, I've not received this bug as was not auto-assigned and I did not check this tracker frequently (issues are mostly tracked on GH).The problem with SSH keys or other authentication mechanisms is that plugin uses  HTTP  REST API to communcate with bitbucket server, thus it uses login\password only.https://github.com/jenkinsci/stashnotifier-plugin/issues/45  
 

  
 
 
 
 

 
 
 

 
 
 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-37238) Problems expanding variables created outside the Jenkins build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-37238  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Problems expanding variables created outside the Jenkins build   
 

  
 
 
 
 

 
 Understand, sorry  
 

  
 
 
 
 

 
 
 

 
 
 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-37238) Problems expanding variables created outside the Jenkins build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37238  
 
 
  Problems expanding variables created outside the Jenkins build   
 

  
 
 
 
 

 
Change By: 
 Pavel Batanov  
 
 
Priority: 
 Critical Minor  
 

  
 
 
 
 

 
 
 

 
 
 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-37238) Problems expanding variables created outside the Jenkins build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-37238  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Problems expanding variables created outside the Jenkins build   
 

  
 
 
 
 

 
 Yeah, really the beta one. I think you should add compatibility section to your pom.xml to warn users that this version is not compatible with earlies ones https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions  
 

  
 
 
 
 

 
 
 

 
 
 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-37238) Problems expanding variables created outside the Jenkins build

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37238  
 
 
  Problems expanding variables created outside the Jenkins build   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alex Earl  
 
 
Components: 
 token-macro-plugin  
 
 
Created: 
 2016/Aug/07 11:15 AM  
 
 
Labels: 
 token-macro  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Pavel Batanov  
 

  
 
 
 
 

 
 Some plugins stopped to work when macros are putted to expand. That worked well before. You can see almost identical stacktrace https://issues.jenkins-ci.org/browse/JENKINS-37222 https://github.com/jenkinsci/stashnotifier-plugin/issues/117  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-37222) Fatal error using the build-name-setter plugin

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov commented on  JENKINS-37222  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Fatal error using the build-name-setter plugin   
 

  
 
 
 
 

 
 Looks like Token Macro Expansion plugin problem. StashNotifier Plugin suffers the exact problem with expanding macros besides the jenkins variables  
 

  
 
 
 
 

 
 
 

 
 
 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-36346) StashNotifier plugin may hang forever if Stash server does not resond properly

2016-07-18 Thread pa...@batanov.me (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pavel Batanov assigned an issue to Pavel Batanov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36346  
 
 
  StashNotifier plugin may hang forever if Stash server does not resond properly   
 

  
 
 
 
 

 
Change By: 
 Pavel Batanov  
 
 
Assignee: 
 Pavel Batanov  
 

  
 
 
 
 

 
 
 

 
 
 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] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-11-26 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 
 
Claude CHOISNET StashNotifier 1.9 has introduced the Credentials Plugin integration. You have to reconfigure old plain credentials to use it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-11-26 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov closed an issue as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28480 
 
 
 
  Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Batanov 
 
 
 

Status:
 
 Open Closed 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov started work on  JENKINS-31117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Pavel Batanov 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31117 
 
 
 
  Plugin should be able to accept a Token Macro  
 
 
 
 
 
 
 
 
 

Change By:
 
 Pavel Batanov 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-31117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin should be able to accept a Token Macro  
 
 
 
 
 
 
 
 
 
 
Implemented. You could try latest snapshot to try TokenMacro expansion 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov edited a comment on  JENKINS-31117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin should be able to accept a Token Macro  
 
 
 
 
 
 
 
 
 
 Implemented. You could try latest snapshot to try TokenMacro expansion https://github.com/jenkinsci/stashnotifier-plugin/releases/tag/1.9-alpha3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

2015-10-23 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-31117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin should be able to accept a Token Macro  
 
 
 
 
 
 
 
 
 
 
I thought, it actually does, but it does not. Currently it could only expand EnvVars. 
Accepeted, thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [stashnotifier-plugin] (JENKINS-31117) Plugin should be able to accept a Token Macro

2015-10-23 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov edited a comment on  JENKINS-31117 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Plugin should be able to accept a Token Macro  
 
 
 
 
 
 
 
 
 
 I thought, it actually does, but it does not. Currently it could only expand EnvVars. Accepeted Accepted , thank you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-10-06 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 
 
Michael Fowler have you resolved your issue? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-10-03 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 
 
Looks like you unchecked "Keep repeated builds in Stash" after the first build has happen. Unfortunately this will not remove builds performed while option was checked. For now you have to options. First is manually mark first build as successfull via the same REST API. Second is just make a dummy commit which will reset builds. 
"Keep repeated builds in Stash" internally just adds the build number from the build key, so then unchecked new bulds overwrite each other and then cheked new build state is created each time instead. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-10-02 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov edited a comment on  JENKINS-28480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 
 Look like the *build keys* are different for these builds. This could happen either if you checked "Keep" checkbox at the settings (which is false, as you've said) or if you've change project name or stash root url between builds.Could you please provide me a raw output of build status list for this changeset. You can find appropriate documentation on how to make a REST API call to your stash server here.https://developer.atlassian.com/static/rest/stash/3.10.0/stash-build-integration-rest.html#idp35424 (GET Request to  {code}  /rest/build-status/1.0/commits/{commitId} {code} ) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [stashnotifier-plugin] (JENKINS-28480) Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)

2015-10-01 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28480 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stash won't update build list when integrated with Jenkins (previous failed build won't allow merge)  
 
 
 
 
 
 
 
 
 
 
Could you check that "keep repeated builds is Stash" option is unchecked both at the jenkins config an at the job config.  Could you please provide a screenshot of your build list (or one with similar problem).  Also I need your stash version to consider more information for investigation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0

2015-05-06 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28134 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Git clone fails since git client plugin 1.17.0  
 
 
 
 
 
 
 
 
 
 
Do I have to try this snapshot plugin with latest Git client plugin? Or stay on 1.16.1? With 1.16.1 it works well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0

2015-05-06 Thread pa...@batanov.me (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Pavel Batanov commented on  JENKINS-28134 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Git clone fails since git client plugin 1.17.0  
 
 
 
 
 
 
 
 
 
 
Mark, looks working with 1.17.0 and snapshot. I'll write here if I get something broken unexpectedly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0

2015-05-02 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-28134


Git clone fails since git client plugin 1.17.0















Kristian, have you restarted jenkins after reverting the plugin?



























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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0

2015-04-29 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-28134


Git clone fails since git client plugin 1.17.0















Since it stands revertable and my jenkins is not mission critical - I can spend some time on testing, so feel free to provide me a link and a bit of instructions if more than just run my jobs is needed.



























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] [git-client-plugin] (JENKINS-28134) Git clone fails since git client plugin 1.17.0

2015-04-29 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-28134


Git clone fails since git client plugin 1.17.0















Mark, reverting helps. So this can be workarounded



























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] [git-client-plugin] (JENKINS-28134) Git clone fails since 1.17.0

2015-04-28 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-28134


Git clone fails since 1.17.0















Experiencing he same issue at 2 of each 3 builds. Either at start of the build or at the end of it. Or both, like this:


Checking out Revision 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9 (refs/remotes/origin/production)
FATAL: String index out of range: -1
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1911)
	at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179)
	at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118)
	at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89)
	at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25)
	at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57)
	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909)
	at hudson.model.AbstractBuild.access$600(AbstractBuild.java:107)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
	at hudson.model.Run.execute(Run.java:1744)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.
Successfully triggered JIRA to update builds of this job
Notified Stash for commit with id 6ff2ffa2f43ae955014c560633d8ce01bc65bcb9
FATAL: String index out of range: -1
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
	at java.lang.String.substring(String.java:1911)
	at hudson.plugins.git.GitChangeSet.isoDateFormat(GitChangeSet.java:179)
	at hudson.plugins.git.GitChangeSet.parseCommit(GitChangeSet.java:118)
	at hudson.plugins.git.GitChangeSet.init(GitChangeSet.java:89)
	at hudson.plugins.git.GitChangeLogParser.parseCommit(GitChangeLogParser.java:73)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:67)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:44)
	at hudson.plugins.git.GitChangeLogParser.parse(GitChangeLogParser.java:25)
	at hudson.scm.ChangeLogParser.parse(ChangeLogParser.java:57)
	at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:909)
	at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:877)
	at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:352)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:675)
	at hudson.model.Run.execute(Run.java:1769)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)




























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















I've tried to dig more data for you


def a = org.kohsuke.stapler.Stapler.currentRequest

a.properties.each { println "$it.key - $it.value" }

println org.kohsuke.stapler.Stapler.currentRequest.dump()



rootPath - https://build.example.com:8080
inputStream - script=def+a+%3D+org.kohsuke.stapler.Stapler.currentRequest%0D%0A%0D%0Aa.properties.each+%7B+println+%22%24it.key+-%3E+%24it.value%22+%7D%0D%0A%0D%0Aprintln+org.kohsuke.stapler.Stapler.currentRequest.dump%28%29json=%7B%22script%22%3A+%22def+a+%3D+org.kohsuke.stapler.Stapler.currentRequest%5Cn%5Cna.properties.each+%7B+println+%5C%22%24it.key+-%3E+%24it.value%5C%22+%7D%5Cn%5Cnprintln+org.kohsuke.stapler.Stapler.currentRequest.dump%28%29%22%2C+%22%22%3A+%22a.properties.each+%7B+println+%5C%22%24it.key+-%3E+%24it.value%5C%22+%7D%22%7DSubmit=%D0%97%D0%B0%D0%BF%D1%83%D1%81%D1%82%D0%B8%D1%82%D1%8C
boundObjectTable - org.kohsuke.stapler.bind.BoundObjectTable@257cd29f
stapler - org.kohsuke.stapler.Stapler@784402ca
servletContext - ServletContext@w.{,file:/var/cache/jenkins/war/},/var/cache/jenkins/war
scheme - https
requestedSessionIdFromCookie - true
requestURLWithQueryString - https://build.example.com:8080/script
cookies - [javax.servlet.http.Cookie@25e7d7f3, javax.servlet.http.Cookie@1812a5f6, javax.servlet.http.Cookie@704dc5d2, javax.servlet.http.Cookie@1f69798, javax.servlet.http.Cookie@645a7d29]
locale - ru
userPrincipal - null
contentLength - 599
pathInfo - /script
parameterMap - [script:[def a = org.kohsuke.stapler.Stapler.currentRequest

a.properties.each { println "$it.key - $it.value" }

println org.kohsuke.stapler.Stapler.currentRequest.dump()], json:[{"script": "def a = org.kohsuke.stapler.Stapler.currentRequest\n\na.properties.each { println \"$it.key - $it.value\" }\n\nprintln org.kohsuke.stapler.Stapler.currentRequest.dump()", "": "a.properties.each { println \"$it.key - $it.value\" }"}], Submit:[Запустить]]
serverName - build.example.com
servletPath - 
serverPort - 8080
restOfPath - 
headerNames - org.eclipse.jetty.http.HttpFields$3@110d0372
attributeNames - java.util.Collections$2@6d5d3a1c
requestedSessionIdFromURL - false
class - class org.kohsuke.stapler.RequestImpl
requestedSessionId - tl3fk9twzq7t5b8ukd04pqu5
bindInterceptor - org.kohsuke.stapler.BindInterceptor@18b57f9f
pathTranslated - /var/cache/jenkins/war/script
authType - null
queryString - null
localAddr - 10.0.0.19
webApp - org.kohsuke.stapler.WebApp@3923c5c
localName - 10.0.0.19
originalRequestURI - /script
method - POST
requestURIWithQueryString - /script
protocol - HTTP/1.0
remotePort - 58921
locales - java.util.Collections$2@75b8bdd8
session - org.eclipse.jetty.server.session.HashedSession:tl3fk9twzq7t5b8ukd04pqu5@867691593
originalRestOfPath - 
dispatcherType - REQUEST
requestURL - https://build.example.com:8080/script
ancestors - [hudson.model.Hudson@60a541a0]
asyncSupported - false
submittedForm - [script:def a = org.kohsuke.stapler.Stapler.currentRequest

a.properties.each { println "$it.key - $it.value" }

println org.kohsuke.stapler.Stapler.currentRequest.dump(), :a.properties.each { println "$it.key - $it.value" }]
requestedSessionIdValid - true
contextPath - 
_javascript_ProxyCall - false
secure - true
remoteHost - 85.30.254.43
remoteUser - null
localPort - 8080
referer - https://build.example.com/script
remoteAddr - 85.30.254.43
contentType - application/x-www-form-urlencoded
parameterNames - java.util.Collections$2@6ff9c725
characterEncoding - UTF-8
asyncStarted - false
requestedSessionIdFromUrl - false
requestURI - /script
request - com.marvelution.jenkins.plugins.jira.filter.OAuthFilter$RequestWrapper@77818791
org.kohsuke.stapler.RequestImpl@58eb7de2 tokens=script ancestors=[hudson.model.Hudson@60a541a0] ancestorsView=[hudson.model.Hudson@60a541a0] stapler=org.kohsuke.stapler.Stapler@784402ca originalRequestURI=/script structuredForm=[script:def a = org.kohsuke.stapler.Stapler.currentRequest

a.properties.each { println "$it.key - $it.value" }

println org.kohsuke.stapler.Stapler.currentRequest.dump(), :a.properties.each { println "$it.key - $it.value" }] parsedFormData=null bindInterceptor=org.kohsuke.stapler.BindInterceptor@18b57f9f request=com.marvelution.jenkins.plugins.jira.filter.OAuthFilter$RequestWrapper@77818791

[JIRA] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections
















println org.kohsuke.stapler.Stapler.currentRequest.rootURL


gives me an exception (truncated output below)


groovy.lang.MissingPropertyException: No such property: rootURL for class: org.kohsuke.stapler.RequestImpl
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
	at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:63)
	at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)
	at Script1.run(Script1.groovy:1)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
	at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
	at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:139)
	at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:111)
	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
	at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:108)
	at jenkins.model.Jenkins._doScript(Jenkins.java:3556)
	at jenkins.model.Jenkins.doScript(Jenkins.java:3533)




























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















I've missed that _buf value is populated with 


StringBuilder buf = _connection.getRequest().getRootURL();

https://github.com/eclipse/jetty.project/blob/master/jetty-server/src/main/java/org/eclipse/jetty/server/Response.java#L666

But the algorithm is the same
It goes to Request
https://github.com/eclipse/jetty.project/blob/master/jetty-server/src/main/java/org/eclipse/jetty/server/Request.java#L1345

And to URIUtil
https://github.com/eclipse/jetty.project/blob/master/jetty-util/src/main/java/org/eclipse/jetty/util/URIUtil.java#L758


public static void appendSchemeHostPort(StringBuilder url,String scheme,String server, int port)
{
if (server.indexOf(':')=0server.charAt(0)!='[')
url.append(scheme).append("://").append('[').append(server).append(']');
else
url.append(scheme).append("://").append(server);

if (port  0)
{
switch(scheme)
{
case "http":
if (port!=80) 
url.append(':').append(port);
break;

case "https":
if (port!=443) 
url.append(':').append(port);
break;

default:
url.append(':').append(port);
}
}
}


I've tried to call

println org.kohsuke.stapler.Stapler.currentRequest.getRootURL()


But still with no success


groovy.lang.MissingMethodException: No signature of method: org.kohsuke.stapler.RequestImpl.getRootURL() is applicable for argument types: () values: []
Possible solutions: getRootPath(), getProtocol(), getCookies(), getRequestURL()
	at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:55)
	at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:46)




























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















Adding these lines from your link helps

proxy_set_header   X-Forwarded-Host $host;
  proxy_set_header   X-Forwarded-Server $host;


As far as I understand Nginx, Location header should be like 'http://10.0.0.19:8080/log/' (upstream ip) to be rewritten properly to 'https://build.example.com/log/'. But it receives 'Location https://build.example.com:8080/log/' and cannot to anything with it.

With these lines to nginx config added now we have


rootPath - https://build.example.com
scheme - https
serverPort - 443
requestURLWithQueryString - https://build.batanov.me/script


Which leads to correct redirection construction



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections













































 
Pavel Batanov
 edited a comment on  JENKINS-27468


Jenkins exposes internal port on redirections
















Adding these lines from your link helps

proxy_set_header   X-Forwarded-Host $host;
  proxy_set_header   X-Forwarded-Server $host;


As far as I understand Nginx, Location header should be like 'http://10.0.0.19:8080/log/' (upstream ip) to be rewritten properly to 'https://build.example.com/log/'. But it receives 'Location https://build.example.com:8080/log/' and cannot to anything with it.

With these lines to nginx config added now we have


rootPath - https://build.example.com
scheme - https
serverPort - 443
requestURLWithQueryString - https://build.example.com/script


Which leads to correct redirection construction



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















These are looking suspicious 


rootPath - https://build.example.com:8080
requestURLWithQueryString - https://build.example.com:8080/script


looks like request is really concatenating with wrong root path



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















Yes, I see. I've tried to dig more.

As far as I understand super() for that place refers to Jetty Response class,

http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.jetty.aggregate/jetty-webapp/8.0.0.v20110901/org/eclipse/jetty/server/Response.java#Response.sendRedirect%28java.lang.String%29

Which initializes path with 

String path=_connection.getRequest().getRequestURI();


Request is Jetty Request, which do the same thing with port there

http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.jetty.aggregate/jetty-all/7.1.0.v20100505/org/eclipse/jetty/server/Request.java#942


public StringBuilder getRootURL()
 {
 StringBuilder url = "" class="code-keyword">new StringBuilder(48);
 String scheme = getScheme();
 int port = getServerPort();
 
 url.append(scheme);
 url.append("://");
 url.append(getServerName());
 
 if (port  0  ((scheme.equalsIgnoreCase("http")  port != 80) || (scheme.equalsIgnoreCase("https")  port != 443)))
 {
 url.append(':');
 url.append(port);
 }
 return url;
 }




























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections













































 
Pavel Batanov
 edited a comment on  JENKINS-27468


Jenkins exposes internal port on redirections
















Yes, I see. I've tried to dig more.

As far as I understand super() for that place refers to Jetty Response class,

http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.jetty.aggregate/jetty-webapp/8.0.0.v20110901/org/eclipse/jetty/server/Response.java#Response.sendRedirect%28java.lang.String%29

Which initializes path with 

String path=_connection.getRequest().getRequestURI();


Request is Jetty Request, which do the same thing with port there

http://grepcode.com/file/repo1.maven.org/maven2/org.eclipse.jetty.aggregate/jetty-all/7.1.0.v20100505/org/eclipse/jetty/server/Request.java#942


public StringBuilder getRootURL()
 {
 StringBuilder url = "" class="code-keyword">new StringBuilder(48);
 String scheme = getScheme();
 int port = getServerPort();
 
 url.append(scheme);
 url.append("://");
 url.append(getServerName());
 
 if (port  0  ((scheme.equalsIgnoreCase("http")  port != 80) || (scheme.equalsIgnoreCase("https")  port != 443)))
 {
 url.append(':');
 url.append(port);
 }
 return url;
 }


Version of jetty in link is not important, they are a bit equal from 7 to 9, as I can see



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















I think, I found problem with Stapler.

https://github.com/stapler/stapler/blob/master/core/src/main/java/org/kohsuke/stapler/ResponseImpl.java#L183-L187


StringBuilder buf = new StringBuilder(req.getScheme()).append("://").append(req.getServerName());
if ((req.getScheme().equals("http")  req.getServerPort()!=80)
|| (req.getScheme().equals("https")  req.getServerPort()!=443))
buf.append(':').append(req.getServerPort());


look the dump above. While scheme is really *https* and serverPort is no *443* (which is 8080), Stapler manually appends port here. Seems like RequestImpl does not know about external port even with *X-Forwarded-Port 443*



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections

2015-03-23 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















I've deployed an old version of jenkins. Tried 1.596 and 1.590. Both had the same. But I think I get a clue.

Nginx as a reverse proxy (http://nginx.org/ru/docs/http/ngx_http_proxy_module.html#proxy_redirect) by default replaces (in my case) http://10.0.0.19:8080/ to https://build.example.com/ as reverse proxy should do. But by some reason nginx get  https://build.example.com:8080/ instead of http://10.0.0.19:8080/ so the replacements does not really occur

Manually adding section

proxy_redirecthttps://build.example.com:8080/ https://build.example.com/;


helps to get rid of this bug. I'll try further investigations to be sure.



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections

2015-03-23 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port on redirections















I've tried to make extended loggin of upstream (jenkins) server and logs really says me that Jenkins return https://build.example.com:8080/log/ for Location header.

Could this be a JRE bug, for example, as soon it is the same even for very old versions?



























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] [core] (JENKINS-27468) Jenkins exposes internal port on redirections

2015-03-22 Thread pa...@batanov.me (JIRA)















































Pavel Batanov
 updated  JENKINS-27468


Jenkins exposes internal port on redirections
















Change By:


Pavel Batanov
(22/Mar/15 1:33 PM)




Summary:


Jenkinsexposesinternalport
whileredirectingtotrailedslashURLsfromno-slashURLs.
onredirections



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















To be honour, port exposig just occures on any internal redirection. Form save, trailing slash redirection, etc. The redirected version contains internal port.



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















Nope, this didn't help. nginx and jenkins were restarted after setting to be sure

After setting X-Forwarded-Port 443

https://build.example.com/
null
https
443
8080


Before setting X-Forwarded-Port 443

https://build.example.com:8080/
null
https
null
8080




























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















Additionaly, I've tried to update everything at the jenkins host, so jenkins is 1.605 now. And still not works



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















Also problem exists only for some routers. I.e

Going /log - redirects me to :8080/log/ (with trailing slash)
Going /systeminfo - succeedes (without trailing slash)
Going /pluginManager - redirects me to :8080/pluginManager/

Harder example is /configure. It opens normally, but redirects me to :8080/ (main page with port) on configuration save



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















Is it possible just to replace jenkins.war with old one (i.e 1.598) just to check it works? Will I have some compatability issues?



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.













































 
Pavel Batanov
 edited a comment on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.
















Is it possible just to replace jenkins.war with old one (i.e 1.598) just to check it works? Will I have any compatability issues?



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.

Pavel Batanov
commented on JENKINS-27468

Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.

The main idea, that nginx config was touched several months ago. And anything worked properly more than for a year.

I've updated nginx to the latest versiona available. I've checked that configuration is equal to the link you refer. (first one, second is not applicable as jenkins is not on the same host)

Here it is for you to be sure

server {

listen *:80;

server_name build.example.com build.other.tld;
rewrite ^/(.*) https://build.example.com/$1;
}

server {

listen *:443;

server_name build.example.com build.other.tld;

location / {
proxy_pass http://10.0.0.19:8080/;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host:$proxy_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_redirect http:// https://;
}
client_max_body_size 400m;

ssl on;
ssl_certificate /root/chain/chained/build.example.com.crt;
ssl_certificate_key /root/chain/keys/build.example.com.key;
}

And firstly I've asked about this bug on a Jenkins IRC chat, and `orrc` confirmed that he has the same behavior.

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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















































Pavel Batanov
 commented on  JENKINS-27468


Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.















But unfortunately it does  I've restarted nginx and jenkins again to be sure.


println org.kohsuke.stapler.Stapler.currentRequest.serverName


gives me


build.example.com


I'll try to deploy old version soon, if we can't find other reason for it



























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] [core] (JENKINS-27468) Jenkins exposes internal port while redirecting to trailed slash URLs from no-slash URLs.