Skip to content

Damien

My feedback

6 results found

  1. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Damien commented  · 

    Logging is essential - especially because:
    * git actions are executed using a different shell (/bin/sh) vs. whatever is configured for the system user (so environment or other nuances may cause unexpected errors)
    * errors are silent and fatal (the commands appear to executed as "command1 && command2", so command2 will only be executed if command1 has a clean exit code)
    * execution starts from the git deploy directory (not the system user home directory), so again this can be a source of user error when specifying the commands
    * troubleshooting and debugging all of the above is awkward: you have to write your own log files (e.g. redirecting command output) which is not at all elegant or intuitive for a typical developer who just wants to get their stuff deployed and working!

  2. 45 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    open discussion  ·  IgorG responded

    Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.

    IG

    Damien supported this idea  · 
  3. 103 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  4. 236 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  5. 54 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
  6. 70 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Damien supported this idea  · 
    An error occurred while saving the comment
    Damien commented  · 

    These are remote services, so they can only scan webpage output. They are defacement monitors.

    The feature here is filesystem based, so it would identify new unknown files, or backend changes to files that may not cause any change to generated HTML)

Feedback and Knowledge Base