We use imported configs to import a deploy job configuration, but have the test configuration specified directly in the travis.yml. As of 6 days ago (April 22) our imported configs resulted in test job build stage running before the deploy stage as expected. As of 5 days ago, that appears to have ch…

Worth noting that I noticed our “Build Config” jobs attribute now looks like this: "jobs": { "include": [ { "stage": "deploy", "name": "Publish with semantic-release", "script": [ "skip" ], "deploy": [ { "provider": "…

Please link to a build, otherwise there’s not enough information. In particular, did you specify stage order ? Without it, the documentation doesn’t specify which order the stages would be in.

Sorry this is a private repo so can’t link to it. I haven’t seen one come up yet in my public repos, but if that happens I sure can. I am not currently specifying the stage order. You make a good point that it is not defined what default order jobs will take. In my head the standard job-lifecycle st…

I was able to specify the stages to control order. I think my core confusion came from the fact that job stages don’t conform to the the phase ordering, even though they generally use the same name convention like deploy in the docs.

[image] richardson-trevor: In my head the standard job-lifecycle stages would get run in the standard job lifecycle order Good point, but stage names are not standardized (except the default stage, “test”). So Travis cannot know how you will call your “deploy” stage. E.g. in one of Travis’ ow…

:+1: Appreciate the pointer in the right direction!

While the docs don’t explicitly specify a default order, this quote from here pretty strongly suggests that test defaults to first: This is mostly useful in order to “prepend” a stage to the test stage that jobs resulting from the matrix expansion will be assigned to. I’ve always understood th…

[image] travi: this quote from here pretty strongly suggests that test defaults to first: Yes, I saw that, and am pretty sure that was the initial intention. But since they didn’t state that explicitly, they likely didn’t make a test for that, and now that they’ve started to juggle with stage…

[image] richardson-trevor: Sorry this is a private repo so can’t link to it. Actually, you can, but only Travis staff members will be able to open that link.

If someone from Travis chimes in here and finds this to be incorrect behavior I’d be happy to shoot them a message with the build link.

Imported config results in out of order build stage

Early Releases

Topic		Replies	Views
Imported config results in out of order build stages despite order explicitly specified Early Releases build-stages , config-import	1	5451	August 12, 2020
Import different files into different jobs Early Releases config-import	3	6340	December 16, 2019
Newcomer question: what are builds, jobs and stages? Travis CI Discussions & Feedback build-stages , travis-yml	9	5502	July 16, 2019
Can't properly use shared configurations via import, enabling it does not result in expected .travis.yml configuration Early Releases config-import	0	5209	October 19, 2020
Build config imports: Merging `deploy` array and objects Feature Requests travis-yml , config-import	3	873	April 15, 2020

Imported config results in out of order build stage

Related topics