Home
Home
Home
Menu highlights
Menu highlights
Update to Allura 1.12.0
Update to Allura 1.12
First step: After the next deployment "codesys export-libdoc" will work, which generates a library documentation in a zip file. Didn't find out if it is possible to create the chm and pdf under linux, yet. In a quick test it didn't work.
Sub
Test 2
a better way to show "cForge updates"?
One part is fixed by the "News Feed", which is in its base a blog. Another thing might be, that we give the users personalized announcements. But the latter is s.th. which will slowly grow in the context of improving the user experience. This is an ongoing topic, and therefore I will close this ticket.
CI / CD Badges
Update to Allura 1.12.0
updated compiler version, so that check all pool objects succeeds
saved library in SP15 binary format to check if Drone works again after that
Home
Home
Home
Home
CI / CD Badges
CI / CD Badges
Home
Home
Home
Home
updated media files
Home
- corrected handling of optional media files
added free default media files to tubetutor
Home
Continuous Integration Beta
Continuous Integration Beta
News Feed
News Feed
where are my artefacts?
The CI/CD created package ended up as a mess!
push
packages auto-update mechanism
Hi Aliazzz, unfortunately that's only possible through the CODESYS Store at the moment.
Support page getting a more prominent link in Home
Not there, but I added one into the menu. Will roll out on next deplopyment. Thanks for the input!
I really don't get it. Beside the *.opt files, you committed all those files into the tags directory v1.0.0.0. So I currently see none which was accidently autogenerated.
You can do so, using your build-scripts, or by placing specific "cp", "mv" or "rm" commands in your .drone.yml When you use the default "codesys" build scripts, you don't need to care about the artifacts, as those commands are copying them already on their own. If you want to have a look into the scripts: https://forge.codesys.com/tol/codesys-4-linux/docker/ci/master/tree/codesys-ide/scripts/
Hi Aliazzz, the package.manifest of package v1.0.0.0 is already exactly yours. It is only auto-generated if there is none found. So yours is taken. The installation problem, which I got was due to a duplicate package Id (maybe only in my, potentially corrupted, installation). But thanks on the input about the additional generated files. This should really not be. BR, Ingo
Hi Aliazzz, I had a quick look, but didn't find what's wrong. I was not able to install the package, but the content looked good. That we pack everything from the subfolder, which contains the package.manifest is a design decission. It makes things a bit easier. We just copy everything, but the package installer installs just the parts, which are defined in the manifest. One thing, is that it makes the package build more simple. The second thing is, that it is also no bad idea to include the sources...
private (disclosed source) project possibilities?
Yes, it is possible. Simply because there are many sane scenarios for that. For example think of a build repository, which contains a private key. Or you maintain a home automation lib, and want to host your private building project on the same platform. So it is OK as long as you don't abuse the service. If you do so, we reserve us the right to delete the project or even the account.
Maybe it's a misunderstanding. The artifacts are not committed to your repository, but placed in a shared folder (see screenshot). The artifacts are by purpose accessible through a link, which you can use directly as a download link. Like this: https://forge.codesys.com/download/tol,cforge,code/...
Flash notifications are not shown
Got it to merge. So it is already fixed in our allura instance.
Flash notifications are not shown