we are using Jenkins <-> Octopus - Plugin. The setup is done but currently we are running octopus server on 2019.9.10 LTS. So the current change from 2019.10 is NOT available … (Package metadata has been renamed to Build Information and promoted to a top level section in the Octopus Library.)
Our Build Process writes the following:
Detected Octopus server version doesn’t support the Build Information API, pushing build information as legacy package metadata: “YourNoteFile”…
Now I have the following questions:
- Where can I find the metadata-package? (can not find it in library)+
- Or should the metadata-Filename be the same name as the before pushed package? for Example: “Webportal.nupkg” --> Push Build-Info: “Webportal” (same name)
The good news here is that we are releasing a new LTS tomorrow which will include the build information update.
In the meantime, yes the metadata package name should be the same between the package and the build information. As for the metadata, if the package Id and version are aligned, when you view the package in the library you should see the build information. It’s also in the DB, if you want to confirm it’s there.
If you have any further questions please let me know,
Hi @Alex.Rolley ,
Package Id and version are aligned --> so this means our metadata-File need to have the same name then the package & is also in the specific Package-View available (where I can see the pushed packages for example 184.108.40.2062-alpha, 220.127.116.113-alpha)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.