[ECMSCC-9366] proceed even if the upstream job is not castable

[jinzishuai]

such as a pipeline job

[allyourbotsarebelongtous]

Build FAILED. See http://jenkins.elasticbox.com/job/ebx_pull_request_jenkins_plugin/567/ for more details.

[gsanchezu]

Hey @julio-castanar, could you please take a look at this one? This is blocking one MSA process.

[jinzishuai]

@julio-castanar FYI, the problem I saw was reported in https://ctl.atlassian.net/browse/ECMSCC-9366

[jinzishuai]

@gsanchezu and @julio-castanar I tried to upload the .hpi file from the artifact into my Jenkins and it was upgraded to the test version correctly however I couldn't run the Jenkins job any more since the TOKEN was not set and in the configure page, I see this error

Is this a bug in the latest master?

[gsanchezu]

Jenkins test this please!

Hey @jinzishuai, the credentials management has changed, so you need to define your token through the credentials plugin (by clicking on the Add button you see, I think). Define a new credentials object of type Token, and then you can use it to connect to your CAM env.

[allyourbotsarebelongtous]

Build FAILED. See http://jenkins.elasticbox.com/job/ebx_pull_request_jenkins_plugin/569/ for more details.

[jinzishuai]

Hey @jinzishuai, the credentials management has changed, so you need to define your token through the credentials plugin (by clicking on the Add button you see, I think). Define a new credentials object of type Token, and then you can use it to connect to your CAM env.

@gsanchezu I did try that. The problem is that none of the created credential would show up in the selection box.

[allyourbotsarebelongtous]

Build FAILED. See http://jenkins.elasticbox.com/job/ebx_pull_request_jenkins_plugin/573/ for more details.