Yes, it does have a main branch, and it looks like the relevant Octopus files are in the .octopus
folder as expected. For some reason they don’t seem to be being read properly when loading the Process for the main
branch. :-/
That’s strange, it’s likely something to do with the project cloning, I take it the main branch of the original project is accessible still?
Would you be able to test something, please?
In the deployment process OCL on the cloned repo, can you modify the template version of the step template from 7 to 8 manually inside the git repo to see if that change is reflected in Octopus?
Kind Regards,
Adam
Oh, it’s worth adding that it doesn’t need to be in all of the steps that use ActionTemplates-6, just in one of them.
I’ve just updated the SQL - Ensure Login - Azure step on the SIP project manually and then pushed the change. Seems to have worked OK!
Note I did this on the main SIP project, not the cloned one
Hi @rik.crompton,
That’s good news! I take it Step 5 is still having issues updating, or could you try this one, too?
Kind Regards,
Adam
In regards to the errors in the cloned project, I wonder if there are references in the repo to the project ID or name that is bound to variables, as any reference to a project variable seems to throw that Sequence contains no matching element error.
You may have to do a search and replace on the cloned repo for any text that is:
“Projects-1” and replace it with “Projects-41”
“SIP” and replace it with “test-update-and-commit”
That should bring everything in line and allow you to view that main branch, in theory.
Kind Regards,
Adam
Still have the problem with Step 5
I couldn’t find any instances of these in the deployment_process.ocl
file. (There were shome references to “SIP”, but they were unrelated to Octopus as far as I could tell)
Okay, I have another theory to test, apologies this is taking so long to get to the bottom of…
Can we try to remove all the steps from the cloned project that reference ActionTemplates-6, except for one of them?
Would you mind if I deleted Steps 4 and 5 from the project “test update and commit”?
Kind Regards,
Adam
Actually, when I look at the Project variables for the cloned project, there’s nothing in there. I guess these are not included in the stuff that’s source controlled?
Go ahead
For info: I have to sign-off for tonight unfortunately. I’ll pick this up again later tonight or tomorrow morning
Thanks for your help with this
No worries! Just some information before you head off for the day:
Removing the other two steps allowed for the template to be updated via the Update and Commit button.
Some reproduction on our end may need to be done to test different use cases with multiple process steps using the same step template.
I’ll update you tomorrow with anything I find!
Kind Regards,
Adam
Hi @rik.crompton,
I’ve just been getting myself up to speed on this issue while Adam and Sean are offline.
You’ve worked through quite a lot in the past 24 hours!
Our Devs working on this have decided it would be an easier option (and to get you going again) for you to manually update the step template versions.
In the deployment_process.ocl
file, please change:
Octopus.Action.Template.Version = "7"
to
Octopus.Action.Template.Version = "8"
and commit it.
They have advised in this case, it will be safe because the change to the library step template did not change any parameters etc.
One important note to consider before making this change is to ensure you don’t accidentally bump the value of the Template.Id.
The Template.Id
is which library step template the process step is based on and the Template.Version
is the version of that library step template. If the Id
value is bumped you may end up with a version that doesn’t exist. Be sure to pay attention to the Template.Id to ensure you are changing the correct step.
I hope this can get you moving in the right direction again at least until we have a fix for this!
Kind regards,
Lauren
Hey @rik.crompton,
You can delete that project now, no worries! Thanks a lot for helping out with my testing.
Kind Regards,
Adam
For customers following this - our engineers have created a Public GitHub Issue so please subscribe to that in order to track updates for when a fix is out. We have found this is not just related to Schema version 4 but will affect customers on all schema versions.
Kind Regards,
Clare
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.