-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JenkinsQueueJob does not work for Jenkins Pipeline Jobs #3135
Comments
Hi @tkp1n, Apologies for the trouble. Jenkins pipelines are supported, so we would appreciate your help in troubleshooting why Jenkins is responding with HTTP 400 ("Project not found") in your case. It appears to be happening on line 208 of the TFS plugin. Can you please reply with the name of the job you are trying to queue, and the versions of Jenkins and the TFS Plugin you are running? Thank you, |
Name of the Pipeline Job (not working): "Atrak" Jenkins Version: 2.19.3 |
It appears the "Pipeline" type in Jenkins 2.19.x is not yet supported in TFS plugin -- it's a new type introduced in the workflow plugin and the current TFS plugin does not have a dependency on it, hence it can't support this type yet. We need to be careful about introduce this dependency since it may break backward compatibility with older servers. |
I see, to bad.. since this new type is really a big plus for building more complex projects. |
We have to same issue. We are moving to TFS and most of our Jenkins projects are Multibranch projects |
Just to be clear, this is a limitation of the TFS Plugin for Jenkins. We should add support in that repo. |
I logged this issue against the TFS Plugin repository: |
TFS plugin 5.3.3 has been released and it supports triggering Pipeline and Multibranch job now. To trigger a Multibranch job, please enter "Jobname/BranchName" as the jobname in the task. |
Is there a way that the queue job from tfs will execute the corresponding branch into jenkins? |
I still keep getting http 400 while queuing the job ! Can any one provide a working screenshot for this ? |
Does anyone has a solution to the above ? I am still getting a 400 while queuing the job for a Multibranch job. @yacaovsnc Should we give the Full url of the job or just the "Jobname/BranchName". And how can we specify the branch name as we need to build all branches in case of Multibranch setup ? |
I have also the setup that I configured Jenkins as a multibranch pipeline. This works fine but not is want to trigger the build for any dynamic created branch by tfs. This dynamically runs my changed branches but If I created a new branch for which there exists no job yet it fails with How should I now adapt my setup? @ricardf you may configure the branch-like I did with $(Build.SourceBranchName) An other problem is that the see also: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml |
The issue as mentioned by @stefaneicher is still not resolved - When create new branches dynamically if no job exists it fails.
When are we gong to see this fixed? |
I have the same probem, On Jenkins :
On Azure devops :
When A push change, I get this error :
azure-pipeline.yml
|
Jenkins Jobs of type Pipeline cannot be triggered from VSTS.
Example result:
(Personal information replaced with
xxx
)The text was updated successfully, but these errors were encountered: