You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A trivial PIP freestyle job yields an empty changeset. This has the added issue of not being able to click details and see who made the delivery.
Steps to reproduce:
Create empty git repository
Put a file in git repository make commit on master branch.
Push to remote master
Configure a PIP job. No special configuration pickup ready branches, merge to master
Allow the job to run its initial build
In repository:
git checkout -b testbranch
echo "changes" > file.txt
git add file.txt
git commit -m "piptest"
git push origin testbranch:ready/testbranch
Allow PIP job to run ( or trigger it ).
It will show something like in the picture above. While I would expect something like the picture below.
Note that we are not squashing or changing history in any way. This is a single commit delivery.
The text was updated successfully, but these errors were encountered:
Yes, and I can see I missed to post my explanation.
The reason why we do not see it as a bug is because it have always been there, and worked that way. Many years ago we didn't succeed with the updating the change log, due to technical issues.
I just remembered wrong, it not a regression.
Does it mean it should be fixed? I don't know, as far as a remember it is actually not possible to update the change log from our plugin according to our developer back then.
The reason is that the change log you see on the job page comes from the SCM part of job, and we our plugin takes over control that object is not write-able any more.
We might have new possibilities now that we're technically inside the plugin not a buildwrapper, but a part of the git scm.
I made issues #93 to investigate if that is possible.
A trivial PIP freestyle job yields an empty changeset. This has the added issue of not being able to click details and see who made the delivery.
Steps to reproduce:
git checkout -b testbranch
echo "changes" > file.txt
git add file.txt
git commit -m "piptest"
git push origin testbranch:ready/testbranch
It will show something like in the picture above. While I would expect something like the picture below.
Note that we are not squashing or changing history in any way. This is a single commit delivery.
The text was updated successfully, but these errors were encountered: