I created an application and created a tag in lifetime. I have set up the pipeline trigger to run a pipeline in jenkins, if I run it manually everything works, but I want it to check the versions of the applications and run the pipeline automatically.
To do this, I set the 'CheckNewVersionsForPipeline' timer but I get the following error "Could not trigger 'Outsystems-CD' because there are still pending changes to be tagged."
What could this be, since there are no pending changes in my application?
Hi Tiago,
Probably by the time the timer runs at least one of the apps within the 'Outsystems-CD' pipeline scope has changes that were not yet tagged.
The timer performs validations based on certain site properties, for your use case maybe you want to check the following ones:
Cheers,
Duarte Castaño DevOps Domain Expert | OutSystems
Hi Duarte,
I only have this application in the pipeline configuration and I don't have any pending changes and the tag version 0.4 has been generated.
Do other applications in the outsystems interfere or does it only matter which one is configured for the pipeline, in this case "TestApp"?
I am having a similar issue, mine is timer CheckNewVersionsForPipeline run with 0s duration and not able to trigger the pipeline to Azure DevOps after I upgrade the version from 2.2.0 to 2.6.0.
When i rollback the version to 2.2.0, the timer works as normal. Anyone has any idea?
I have check the timer logs, no errors.
Hi @Duarte Castaño - Do you have any idea of the timer problem i facing?
Hi Xiao,
As mentioned in the release notes, the CheckNewVersionsForPipeline timer is now used to trigger CI/CD pipelines based on a predefined schedule when changes are detected.
To resolve your issue, ensure you've correctly specified which triggers should activate the pipeline on a schedule. This configuration can be found on the pipeline's configuration screen, under the "Trigger on Schedule" setting (the pipeline will trigger depending on the enabled features, as I explained in my previous reply).
hi @Duarte Castaño - I have checked the Trigger on schedule, but it does works. It shows a valid service account token must be configured.
I did not change the pipeline server credentials, may I know if the service account token is referring to which value?
Hi @Duarte Castaño - The token issue is resolved. Now i have another issue, please see picture below:
are these the correct URL to use?
Thanks in advanced.
Yes, you need to set up those before you use the component.Here are some follow-up steps to help you set up the needed configs.
Best regards,Duarte Castaño DevOps Domain Expert | OutSystems
Thanks for replying. I have done the setup but now hitting 403 forbidden when the timer run. Calling the lifetime API is internal i suppose, am i correct?
You need to implement authentication when calling the lifetime API, see:https://success.outsystems.com/documentation/11/reference/outsystems_apis/lifetime_api_v2/rest_api_authentication/
Yes, I have created an service account and put the token at the site properties, I still getting the 403 error.
When I rollback to previous version, even the deployment API default URL restored to the default, it can work.
I cannot understand how it works.
I follow the step by step guide to setup as well, but just not working for the latest version.
Yes, the Trigger Pipeline Plugin uses the LifeTime API to get all the needed information and perform actions to trigger pipelines.
Please make sure the service account you've provided has enough privileges.