-
Notifications
You must be signed in to change notification settings - Fork 93
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
Whitelist does not work if pipeline has an upstream pipeline as material #50
Comments
You'll have to be more specific about what are your expectations. Could you elaborate a bit? |
You're right, my example is a bit off, so I'm going to provide a slightly different use case with more detail. I will need to test it in a short PoC though, to confirm that it's still a bug. In my case
Now, If only So in my case, I am sure that changes in => As promised, I will return with a confirmed example. |
There is one minor bug that I am aware of. If you are introducing whitelist/blacklist change in current commit |
Thanks. It still does not work the way I expect (tested multiple times). Here is my config:
Then, if make a change inside If I removed => It's like whitelists/blacklists are ignored when upstream pipelines are used. |
OK, but does pr2 and pr3 get triggered only after p1 was built? If so then it is expected. Above looks similar to first config you posted, but it has additional p3, which should not matter much. If you configure this with XML (via UI), I believe it would behave the same. The p2 or p3 are built because p1 was built and it is a dependency. You cannot "blacklist" triggers caused by one of dependency pipelines. |
Yes.
This is unfortunate, as here I don't need an OR-condition for triggering, but an AND-condition (if that makes sense). It looks like that the material configuration is not as sophisticated... If the XML behaves the same, then I conclude that the right support channel is the GoCD authors, not here. Thanks for your help though. |
You should look into user forum - https://groups.google.com/forum/#!forum/go-cd Above behavior is the CD-way because in your case, you have built a new library in p1, which is used by p2 and p3. The change in library could be breaking either of the end user projects, which is why both must be built. |
I understand your argument, but in my case:
=> I'll contact the GoCD group. |
If you don't want |
Thanks for the tip, @arvindsv, in fact you are right, but I tried it, and it's even worse: failed for the first 2 test cases below: Test Case 1
Problem: all 3 builds were executed. Test Case 2
Problem: no builds were executed. (Incorrect => serious issue.) Test Case 3
Worked. |
I contacted the developers directly, I think we should continue the conversation there (see the referenced issue). |
Update: I had to correct my example, please see #50 (comment).
In a nutshell I have this config:
Now if I commit something outside of
some-dir
, I expectp2
not triggered, but it does, both pipelines are built. That sounds wrong. The whitelisting works fine if I removep1-as-upstream
from thep2
materials.Do you know why it is not working? Is it a YAML config plugin bug or a GoCD bug?
The text was updated successfully, but these errors were encountered: