Activity for Ingo

  • Ingo Ingo modified ticket #61

    Flash notifications are not shown

  • Ingo Ingo posted a comment on ticket #61

    Will be fixed in Allura. Can't be easily merged. https://forge-allura.apache.org/p/allura/tickets/8312/

  • Ingo Ingo created ticket #61

    Flash notifications are not shown

  • Ingo Ingo modified ticket #60

    .drone-artifacts directory troubles

  • Ingo Ingo modified a wiki page

    Licensing

  • Ingo Ingo posted a comment on ticket #60

    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.

  • Ingo Ingo posted a comment on ticket #60

    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

  • Ingo Ingo committed [r18]

    added build package

  • Ingo Ingo committed [r17]

    added test

  • Ingo Ingo committed [r16]

    corrected working path

  • Ingo Ingo committed [r15]

    removed manual copy of build artifacts from drone.yml

  • Ingo Ingo committed [r14]

    create artifacts directory

  • Ingo Ingo committed [r13]

    test to fake result

  • Ingo Ingo posted a comment on ticket #59

    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

  • Ingo Ingo committed [r70]

    Autoversioning commit: a non-deltaV client made a change to

  • Ingo Ingo committed [r69]

    Autoversioning commit: a non-deltaV client made a change to

  • Ingo Ingo committed [r68]

    Autoversioning commit: a non-deltaV client made a change to

  • Ingo Ingo created a blog post

    Licenses of projects

  • Ingo Ingo created a wiki page

    Licensing

  • Ingo Ingo modified a wiki page

    IndexMain

  • Ingo Ingo modified ticket #58

    CI CD menu under admin

  • Ingo Ingo posted a comment on ticket #58

    BTW: This is the page, which I would expect to open for cfUnit: https://forge.codesys.com/build-status/prj/cfunit/build-log.html

  • Ingo Ingo posted a comment on ticket #58

    Crazy! With your allowance I will login with your user to check it.

  • Ingo Ingo posted a comment on ticket #58

    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.

  • Ingo Ingo modified a wiki page

    IndexMain

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo committed [5a5d65]

    test

  • Ingo Ingo committed [89e5e8]

    test rebuild

  • Ingo Ingo modified ticket #57

    setting a project to "inactive" status

  • Ingo Ingo posted a comment on ticket #57

    no worries. but it shows, that project status and rights should be better described, or easier to configure.

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified a wiki page

    Home

  • Ingo Ingo modified ticket #46

    last page update

  • Ingo Ingo posted a comment on ticket #46

    Sadly not as easy as it sounds. Sorry for the moment.

  • Ingo Ingo modified ticket #55

    SEO

  • Ingo Ingo posted a comment on ticket #55

    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.

  • Ingo Ingo modified ticket #53

    Explaining the new Rate system?

  • Ingo Ingo modified ticket #53

    Explaining the new Rate system?

  • Ingo Ingo modified ticket #53

    Explaining the new Rate system?

  • Ingo Ingo posted a comment on ticket #53

    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

  • Ingo Ingo created a wiki page

    Discussions

  • Ingo Ingo modified a wiki page

    IndexMain

  • Ingo Ingo modified a wiki page

    Permissions

  • Ingo Ingo posted a comment on ticket #52

    A good read: https://gist.github.com/dupuy/1855764

  • Ingo Ingo modified ticket #52

    .rst markup language support for Allura?

  • Ingo Ingo posted a comment on ticket #52

    Hi Aliazzz, I was thinking about that a bit. While it sounds very true, that things become better reusable, I have no clue about the actual use cases, yet. What I can imagine: You export library documentation and want to include this in your Wiki. Are there other use cases, which you thought of? BR, Ingo

  • Ingo Ingo posted a comment on ticket #50

    This is not exactly possible. But you can install ablanding page if you like: https://forge.codesys.com/forge/wiki/Landing%20Page/

<< < 1 .. 10 11 12 >