I have the feeling that the latest changes aren't always reflected to the repository. I have a github repository (set to very frequent == 30 seconds). However when I start the build it does not always contain the latest data.
I also have an issue with a trigger which does not seem to work (on the same repository). To investigate I would really like to see the repository changes (last 5 or something like that) to see the actual status of a repository (has it fetched my latest changes?).
If you look at the Changes tab on the Configuration you should see all the changesets from all the repositories attached to the Config :
Attachment unavailable
Thanks. That’s what I use to check, but then I have to start a build first. What I do now is:
1) Start a build
2) Go to changes tab
3) Notice that it hasn’t used the latest changeset
4) Stop the build
5) Reset the repository, start at 1
That’s why it would be great if I can just see the changes of a repository on the same screen as the reset option.
So are new changes showing up after you reset the repository? If so then thats a problem. When you start a build, it actually tells the repo to check for new changes, to make sure we are building the latest changes.
What settings do you have on the repository and the trigger? The branch settings may be why you are not seeing the changes.
This is one without a trigger (manual start).
What about the repository. Is it set to look at All Branches?
Single branch (develop), which I know has a change (we actively develop on the “develop” branch, we run production builds from “master” branch).
See this repository: https://github.com/catel/catel
Ok, I will set up a config here with that repo and track changes. I am wondering if it has something to do with github going down occasionally (which seems to be getting more frequent).