Activity for Ingo
-
Ingo posted a comment on ticket #67
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
-
Flash notifications are not shown
-
Will be fixed in Allura. Can't be easily merged. https://forge-allura.apache.org/p/allura/tickets/8312/
-
Flash notifications are not shown
-
.drone-artifacts directory troubles
-
Licensing
-
I think it is a misunderstanding. The last example .drone.yml on the linked page shows the usage. In fact you just add the linux command to copy the artifact to the end of your .drone.yml.file. Other tools and scripts, which you maybe execute for testing on your windows host should not known anything about that folder.
-
Hi Aliazzz, first, windows accepts a dot in folder names like all others. Second, what do you try to achieve? The directory is only used during continuous integration. The directory name should only be used in drone helper scripts (like the codesys-ide:local), or inside of a .drone.yml file. The latter is described here: https://forge.codesys.com/forge/wiki/Continuous%20Integration/ BR, Ingo
-
added build package
-
added test
-
corrected working path
-
removed manual copy of build artifacts from drone.yml
-
create artifacts directory
-
test to fake result
-
Hi Aliazzz, like always: thanks for the input. I thought about it already, but don't have a solution, yet. The blog post is a workaround for me for the moment. BR, Ingo
-
Autoversioning commit: a non-deltaV client made a change to
-
Autoversioning commit: a non-deltaV client made a change to
-
Autoversioning commit: a non-deltaV client made a change to
-
Licenses of projects
-
Licensing
-
IndexMain
-
CI CD menu under admin
-
BTW: This is the page, which I would expect to open for cfUnit: https://forge.codesys.com/build-status/prj/cfunit/build-log.html
-
Crazy! With your allowance I will login with your user to check it.
-
Can you be more precise? The system is not completed, yet. As some CODESYS features are missing, but the menu should work. You should get a report with a list of artifacts.
-
IndexMain
-
Home
-
test
-
test rebuild
-
setting a project to "inactive" status
-
no worries. but it shows, that project status and rights should be better described, or easier to configure.
-
Home
-
Home
-
Home
-
Home
-
Home
-
last page update
-
Sadly not as easy as it sounds. Sorry for the moment.
-
SEO
-
Hi Aliazzz, some of the options will be removed when the style of the statistics will be fixed. But with the keyphrases, you are right. This is a non-critical and important feature, when s.o. seriously optimizes his descriptions for Google. Seems as this is a limitation of goaccess, which we are using to get the statistics. I hope, that I applied a good enough workaround.
-
Explaining the new Rate system?
-
Explaining the new Rate system?
-
Explaining the new Rate system?
-
Hi Aliazzz, I wrote a small help page. Hope it explains it for you. If not, let me know. https://forge.codesys.com/forge/wiki/Discussions/ BR, Ingo
-
Discussions
-
IndexMain
-
Permissions