- Publish Your Build
- Signing off Process
Publish Your Build
Step 1 - Build using the Build Central from CET Developer.
In the Build Central, under the Build tab:
- Firstly select the Release type build is selected by default. You can leave it at that if this build is intended to be an official release. Otherwise, select Beta.
- Select the git repository to be built.
- Select the extensions under the git repository to be built by right-clicking each column.
- Then, press Build Release and wait for it to be done. It'll look green like this when it's successfully completed, otherwise it'll look reddish with the build error shown in the logs below:
Step 2 - Upload the Build to MyConfigura's Build Center
After the build is successful, switch to the Upload tab. Check to see if the built extensions are the ones you want to upload, if not, right-click on the extension columns to select and deselect.
By default, there is no need to rename the auto-generated name in the Name for upload batch. It is used to list and find this specific build in MyConfigura's Build Center.
Pressing the Upload button will begin uploading the build to MyConfigura's Build Center.
Step 3 - Place your Build under the Official Distributions in MyConfigura's Build Center.
If the build is successfully uploaded from CET Developer's Build Central, it should now show under the Builds in Build Center. You can find it by typing in the name used in Name for upload batch in CET Developer's Build Central.
When you want to publish to Beta or RC, it is usually done under Custom Distribution on the Build Center page. If you are ready to publish your official version, you can add your build to the Official Distribution. You can follow the help article here on how.
We highly recommend you to drop your builds as such:
- For Major release:
- Drop your builds into X.X-MAJOR-BETA/RC
- OR, create a custom box that inherits from X.X-MAJOR-BETA/RC
- For patches:
- Drop your builds into X.X-PATCHY
- OR, create a custom box that inherits from X-X-PATCHY
- OR, update a custom box setting it to inherit from X-X-PATCHY
Build Center on the MyConfigura page is divided into Official and Custom Distribution.
Why Place Your Build in the CET build box?
To emulate and test how CET is used by the majority of our users, where multiple extensions are installed and used simultaneously, Configura needs all extensions to be available in the CET build box.
Signing off Process
A signing off process is primarily done by the Extension Owners and Developer Admins. It is to ensure that the new build has been tested and includes a planned release date.
By doing this process:
- Support can plan in advance to let the users know the release dates of the Extensions. For example, let us say that a user has multiple Extensions installed in their CET and there is one Extension that has not been released to the new version yet. So when a user tries to open a saved drawing, the products from that outdated Extension will not appear on the drawing. This will cause a lot of confusion amongst users, but if Support publicized the dates beforehand to the users, they will understand the circumstances.
- QA can plan ahead for when they can perform the live update test on your Extension.
- Support will be aware that there will be a spike in the number of tickets from users during that period of release and can allocate time accordingly to fix those bugs on time.
- If a user asks when he/she can update to the new version of your Extension, Support can inform the user of the exact date of release.
- Once QA has signed off, the release dates go in the list of build details which gives Support an overview of all the Extensions to avoid any delays or drastic changes on the release date.
More details on signing off on Extension testing can be here.
Once signed, the version will be marked as Signed to notify Configura that you have completed the test.