Skip to main content

Posts

Showing posts with the label directory

Jenkins: publish over ssh does not put files to remote server

Problem : I have strange issue on the latest Jenkins 1.634. Publish over ssh writes to log that it puts correctly file but nothing appears on remote server. e.g. I have logs SSH: cd  [var/www/data-fb-localtest] SSH: OK SSH: put  [asm.js] SSH: OK SSH: put  [asm.js.gz] SSH: OK SSH: put  [hero.data] SSH: OK SSH: put  [hero_main.js] SSH: OK SSH: cd  [/home/dev] SSH: OK SSH: cd  [var/www/data-fb-localtest/] SSH: OK SSH: put  [achievements.exm] SSH: OK SSH: put  [ai.exm] SSH: OK SSH: put  [atlas0.atlas] SSH: OK SSH: put  [atlas0.rgbz] SSH: OK but nothing appears in var/www/data-fb-localtest Solution : I found the issue. I do not set root remote directory and in publish task use absolute path. But plugin does use not absolute path but path relative to my user’s home directory

Jenkins – Publish Over SSH Plugin: How to copy directory

Problem: I’m trying to use  Jenkins’ Publish Over SSH  plugin to copy all files AND sub-directories of some given directory, but so far, I’ve only able to copy files and NOT directory. I have a directory named  foo  in my workspace, and during the build, I want to copy everything in this directory to a remote server. I’ve tried this pattern  foo/** , but it doesn’t copy all sub-directories. Solution: For recursive copy of directory you should give foo/**/*

Setting your username in Git

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you’d like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository whe...

Setting your username in Git

Git uses a username to associate commits with an identity. The Git username is not the same as your GitHub username. You can change the name that is associated with your Git commits using the  git config  command. The new name you set will be visible in any future commits you push to GitHub from the command line. If you'd like to keep your real name private, you can use any text as your Git username. Changing the name associated with your Git commits using  git config  will only affect future commits and will not change the name used for past commits. Setting your Git username for  every  repository on your computer Open  Git Bash . Set a Git username: $ git config --global user.name " Mona Lisa " Confirm that you have set the Git username correctly: $ git config --global user.name > Mona Lisa Setting your Git username for a single repository Open  Git Bash . Change the current working directory to the local repository where you want to configure the name tha...

Jenkins - Publish Over SSH Plugin: How to copy directory

Problem: I'm trying to use  Jenkins' Publish Over SSH  plugin to copy all files AND sub-directories of some given directory, but so far, I've only able to copy files and NOT directory. I have a directory named  foo  in my workspace, and during the build, I want to copy everything in this directory to a remote server. I've tried this pattern  foo/** , but it doesn't copy all sub-directories. Solution: For recursive copy of directory you should give foo/**/*

Jenkins: publish over ssh does not put files to remote server

Problem : I have strange issue on the latest Jenkins 1.634. Publish over ssh writes to log that it puts correctly file but nothing appears on remote server. e.g. I have logs SSH: cd  [var/www/data-fb-localtest] SSH: OK SSH: put  [asm.js] SSH: OK SSH: put  [asm.js.gz] SSH: OK SSH: put  [hero.data] SSH: OK SSH: put  [hero_main.js] SSH: OK SSH: cd  [/home/dev] SSH: OK SSH: cd  [var/www/data-fb-localtest/] SSH: OK SSH: put  [achievements.exm] SSH: OK SSH: put  [ai.exm] SSH: OK SSH: put  [atlas0.atlas] SSH: OK SSH: put  [atlas0.rgbz] SSH: OK but nothing appears in var/www/data-fb-localtest   Solution : I found the issue. I do not set root remote directory and in publish task use absolute path. But plugin does use not absolute path but path relative to my user's home directory

fswatch – Monitors Files and Directory Changes or Modifications in Linux

fswatch  is a cross-platform, file change monitor that gets notification alerts when the contents of the specified files or directories are altered or modified. It executes four types of monitors on different operating systems such as: A monitor build on the File System Events API of Apple OS X. A monitor based on  kqueue , a notification interface present in FreeBSD 4.1 also supported on many *BSD systems, OS X inclusive. A monitor based on File Events Notification API of the Solaris kernel plus its spin-offs. A monitor based on inotify, a kernel subsystem that shows file system modifications to apps. A monitor based on ReadDirectoryChangesW, a Windows API that records alters to a directory. A monitor that regularly check that status of file system, keeps file modification times in memory, and manually determine file system changes (which works anywhere, where stat can be used). Features of fswatch Supports several OS-specific APIs Allows recursive directory ...

fswatch – Monitors Files and Directory Changes or Modifications in Linux

fswatch is a cross-platform, file change monitor that gets notification alerts when the contents of the specified files or directories are altered or modified. It executes four types of monitors on different operating systems such as: A monitor build on the File System Events API of Apple OS X. A monitor based on kqueue , a notification interface present in FreeBSD 4.1 also supported on many *BSD systems, OS X inclusive. A monitor based on File Events Notification API of the Solaris kernel plus its spin-offs. A monitor based on inotify, a kernel subsystem that shows file system modifications to apps. A monitor based on ReadDirectoryChangesW, a Windows API that records alters to a directory. A monitor that regularly check that status of file system, keeps file modification times in memory, and manually determine file system changes (which works anywhere, where stat can be used). Features of fswatch Supports several OS-specific APIs Allows recursive directory monitoring ...

Pyinotify – Monitor Filesystem Changes in Real-Time in Linux

Pyinotify  is a simple yet useful Python module for monitoring filesystems changes in real-time in Linux. As a System administrator, you can use it to monitor changes happening to a directory of interest such as web directory or application data storage directory and beyond. It depends on  inotify  (a Linux kernel feature incorporated in kernel 2.6.13), which is an event-driven notifier, its notifications are exported from kernel space to user space via three system calls. The purpose of  pyinotify  is to bind the three system calls, and support an implementation on top of them providing a common and abstract means to manipulate those functionalities. In this article, we will show you how to install and use pyinotify in Linux to monitor filesystem changes or modifications in real-time. Dependencies In order to use  pyinotify , your system must be running: Linux kernel 2.6.13 or higher Python 2.4 or higher How to Install Pyino...

Pyinotify – Monitor Filesystem Changes in Real-Time in Linux

Pyinotify is a simple yet useful Python module for monitoring filesystems changes in real-time in Linux. As a System administrator, you can use it to monitor changes happening to a directory of interest such as web directory or application data storage directory and beyond. It depends on inotify (a Linux kernel feature incorporated in kernel 2.6.13), which is an event-driven notifier, its notifications are exported from kernel space to user space via three system calls. The purpose of pyinotify is to bind the three system calls, and support an implementation on top of them providing a common and abstract means to manipulate those functionalities. In this article, we will show you how to install and use pyinotify in Linux to monitor filesystem changes or modifications in real-time. Dependencies In order to use pyinotify , your system must be running: Linux kernel 2.6.13 or higher Python 2.4 or higher How to Install Pyinotify in Linux First start by checking the kernel and Python ...