[JIRA] [ghprb-plugin] (JENKINS-31436) Job configuration of GitHub Pull Request Builder credentials doesn't save

2016-02-04 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich edited a comment on  JENKINS-31436 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job configuration of GitHub Pull Request Builder credentials doesn't save  
 
 
 
 
 
 
 
 
 
 Jenkins 1.638org.jenkins-ci.plugins:ghprb:1.29.8 Credentials are actually saved in job configuration.They fail to load on subsequent job configuration edit.Test steps: - create two sets of credentials on /configure page in GitHub Auth section - create a job using Github Pull Request Builder - edit job configuration - select non-default (second) credential  in  GitHub API credentials field - save job configuration - observe change in job config history, gitHubAuthId is updated - edit job configuration Expected: second credentials are selected Actual: default credential are selected If job configuration is saved without any changes, gitHubAuthId will again assume default value.Workaround: whenever you edit job configration, select credentials again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [ghprb-plugin] (JENKINS-31436) Job configuration of GitHub Pull Request Builder credentials doesn't save

2016-02-04 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich edited a comment on  JENKINS-31436 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job configuration of GitHub Pull Request Builder credentials doesn't save  
 
 
 
 
 
 
 
 
 
 Credentials are actually saved in job configuration.They fail to load on subsequent job configuration edit.Test steps: - create two sets of credentials on /configure page in GitHub Auth section - create a job using Github Pull Request Builder - edit job configuration - select non-default (second) credential  in  GitHub API credentials field - save job configuration -  observe change in job config history, gitHubAuthId is updated -  edit job configuration Expected: second credentials are selected Actual: default credential are selected  If job configuration is saved without any changes, gitHubAuthId will again assume default value. Workaround: whenever you edit job configration, select credentials again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [ghprb-plugin] (JENKINS-31436) Job configuration of GitHub Pull Request Builder credentials doesn't save

2016-02-04 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich commented on  JENKINS-31436 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job configuration of GitHub Pull Request Builder credentials doesn't save  
 
 
 
 
 
 
 
 
 
 
Credentials are actually saved in job configuration. They fail to load on subsequent job configuration edit. Test steps: 
 

create two sets of credentials on /configure page in GitHub Auth section
 

create a job using Github Pull Request Builder
 

edit job configuration
 

select non-default (second) credential in GitHub API credentials field
 

save job configuration
 

edit job configuration
 
 
Expected: second credentials are selected  Actual: default credential are selected  
Workaround: whenever you edit job configration, select credentials again. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [artifactdeployer-plugin] (JENKINS-30257) Download links are broken after reconfiguration

2015-09-02 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30257 
 
 
 
  Download links are broken after reconfiguration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vasili Gulevich 
 
 
 
 
 
 
 
 
 
 Affects Artifact Deployer plugin version 0.33Test steps:* Configure a job that deploys some artifacts to /prefix/path1* Build a one or two builds of this job* Change its configuration to deploy to /prefix/path2Expected result:All builds should have working links for artifact download (by either moving existing artifacts to new location, or keeping old links to previously built ones)Actual result:Older builds have broken download links referencing /prefix/path2, which is  not  only  populated  by newer builds . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [artifactdeployer-plugin] (JENKINS-30257) Download links are broken after reconfiguration

2015-09-02 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30257 
 
 
 
  Download links are broken after reconfiguration  
 
 
 
 
 
 
 
 
 

Change By:
 
 Vasili Gulevich 
 
 
 
 
 
 
 
 
 
 Affects Artifact Deployer plugin version 0.33 Test steps:* Configure a job that deploys some artifacts to /prefix/path1* Build a one or two builds of this job* Change its configuration to deploy to /prefix/path2Expected result:All builds should have working links for artifact download (by either moving existing artifacts to new location, or keeping old links to previously built ones)Actual result:Older builds have  brokendownload  broken download  links referencing /prefix/path2, which is not populated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [artifactdeployer-plugin] (JENKINS-30257) Download links are broken after reconfiguration

2015-09-01 Thread v.v.gulev...@mail.ru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Vasili Gulevich created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-30257 
 
 
 
  Download links are broken after reconfiguration  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Gregory Boissinot 
 
 
 

Components:
 

 artifactdeployer-plugin 
 
 
 

Created:
 

 02/Sep/15 6:57 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Vasili Gulevich 
 
 
 
 
 
 
 
 
 
 
Test steps: 
 

Configure a job that deploys some artifacts to /prefix/path1
 

Build a one or two builds of this job
 

Change its configuration to deploy to /prefix/path2
 
 
Expected result: All builds should have working links for artifact download (by either moving existing artifacts to new location, or keeping old links to previously built ones) 
Actual result: Older builds have brokendownload links referencing /prefix/path2, which is not populated.