Teamcity- has not .gitmodules configuration in the root directory - asp.net-mvc-4

Facing Issue On Teamcity --
Failed to build patch for build #27 {build id=3317287, buildTypeId=ABC_AbcTestBuild_BuildAbcTest}, VCS root: "ABC_VCS_Root" {instance id=59887, parent internal id=12858, parent id=ABCProj_ABCTestBuild_AbcVcsRoot, description: "https://abc#stash.abc.git#refs/heads/ABC_Dev_CreateEditMerge"}, due to error: 'build patch' command failed.
stderr: The 'https://abc#stash.abc.git' repository has a submodule in the 'f1e673f5b8670a1d978434cd0a9275491c34c253bf' commit at the 'abc' path, but has not .gitmodules configuration in the root directory

Related

meshcat_visualizer_test fails fetching repository 'yaml_cpp'

I'm trying to run drake/bindings/pydrake/systems/test/meshcat_visualizer_test.py as per the commented instructions at the top of said file, but I am unfamiliar as to how I would add yaml-ccp, which I believe is causing errors. I have the drake repo cloned and pydrake configured, and was able to Run Server (the first required command), but do not know how to add the yaml-cpp package if it is missing.
phil#philpc:~/drake/bindings/pydrake/systems/test$ bazel run --run_under='env TEST_ZMQ_URL=tcp://127.0.0.1:6000' //bindings/pydrake/systems:py/meshcat_visualizer_test -- 'TestMeshcat.test_point_cloud_visualization'
INFO: Repository yaml_cpp instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule pkg_config_repository defined at:
/home/phil/drake/tools/workspace/pkg_config.bzl:276:25: in <toplevel>
ERROR: An error occurred during the fetch of repository 'yaml_cpp':
Unable to complete pkg-config setup for #yaml_cpp repository: error 1 from [/usr/bin/pkg-config, "yaml-cpp"]:
INFO: Repository remotejdk11_linux instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
/home/phil/.cache/bazel/_bazel_phil/a5ca8dfa5bc97606d4bf1d23312635a2/external/bazel_tools/tools/build_defs/repo/http.bzl:336:16: in <toplevel>
INFO: Repository remote_java_tools_linux instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
/home/phil/.cache/bazel/_bazel_phil/a5ca8dfa5bc97606d4bf1d23312635a2/external/bazel_tools/tools/build_defs/repo/http.bzl:336:16: in <toplevel>
INFO: Repository fmt instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule _github_archive_real defined at:
/home/phil/drake/tools/workspace/github.bzl:102:24: in <toplevel>
INFO: Repository lcm instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule _github_archive_real defined at:
/home/phil/drake/tools/workspace/github.bzl:102:24: in <toplevel>
ERROR: /home/phil/drake/tools/install/libdrake/BUILD.bazel:251:1: //tools/install/libdrake:libdrake_runtime_so_deps depends on #yaml_cpp//:yaml_cpp in repository #yaml_cpp which failed to fetch. no such package '#yaml_cpp//': Unable to complete pkg-config setup for #yaml_cpp repository: error 1 from [/usr/bin/pkg-config, "yaml-cpp"]:
ERROR: Analysis of target '//bindings/pydrake/systems:py/meshcat_visualizer_test' failed; build aborted: no such package '#yaml_cpp//': Unable to complete pkg-config setup for #yaml_cpp repository: error 1 from [/usr/bin/pkg-config, "yaml-cpp"]:
INFO: Elapsed time: 0.515s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (6 packages loaded, 0 targets configured)
FAILED: Build did NOT complete successfully (6 packages loaded, 0 targets configured)
Try running /usr/bin/pkg-config yaml-cpp --libs on the command line and see what happens. It should report no error and just print -lyaml-cpp.
Have you installed Drake's dependencies using https://drake.mit.edu/ubuntu.html command? It should have installed libyaml-cpp-dev at that point, which should be all that is needed for pkg-config to succeed.

meson.build: ERROR: File does not exist, while in reality it does

From a trivial meson.build file, I get the following error:
meson.build:27:0: ERROR: File dataStructures.hpp does not exist.
dataStructures.hpp,
The meson.build file is:
headers += [
'dataStructures.hpp',
'interface.hpp',
'platform.hpp',
'progArgs.hpp',
]
The file reported as missing is present and it is in the same directory the meson.build file is.
If I remove the 'dataStructures.hpp' string from the list, I get the same error for the second file 'interface.hpp'.
What am I doing wrong?
More details follow.
> CC=clang CXX=clang++ meson /dev/shm/test-build
The Meson build system
Version: 0.52.0
Source dir: /home/pietrom/myProgs/test
Build dir: /dev/shm/test-build
Build type: native build
Project name: test
Project version: 0.0.1
C++ compiler for the host machine: clang++ (clang 8.0.1 "clang version 8.0.1 (tags/RELEASE_801/final)")
C++ linker for the host machine: GNU ld.bfd 2.32
Host machine cpu family: x86_64
Host machine cpu: x86_64
src/meson.build:27:0: ERROR: File dataStructures.hpp does not exist.
A full log can be found at /dev/shm/test-build/meson-logs/meson-log.txt
In the full log there is no much more than what already reported.
This is the project directory structure:
test/
meson.build
src/
meson.build
sources
config/
meson.build
sources
testers/
meson.build
sources
utilities/
meson.build
sources
As you don't provide all meson.build file contents, and most importantly the place where it happens - meson.build:27:0: ERROR: File dataStructures.hpp does not exist. - points at line 27 in some meson.build file, I'll try to make a guess that you build executable in root meson.build file, i.e. in test/meson.build however your headers are inside test/src. If that's the case, you don't need to have this array of headers at all, just add
inc = include_directories('./src')
some_test_exe = executable('mytest',
test_sources,
...
include_directories : inc
)
include_directories function creates include object with path relative to your source root.

Unable to build ODL sdn controller code .?

I have downloaded the code using
git clone https://git.opendaylight.org/gerrit/p/integration/distribution.git
When I try to build this, it shows following error.
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.opendaylight.integration:root:0.5.0-SNAPSHOT: Could not find artifact org.opendaylight.odlparent:odlparent:pom:1.7.0-SNAPSHOT and 'parent.relativePath' points at no local POM # line 4, column 11
#
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.opendaylight.integration:root:0.5.0-SNAPSHOT (/home/controller/distribution/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.opendaylight.integration:root:0.5.0-SNAPSHOT: Could not find artifact org.opendaylight.odlparent:odlparent:pom:1.7.0-SNAPSHOT and 'parent.relativePath' points at no local POM # line 4, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
You need to make sure your settings.xml points to the OpenDaylight Nexus artifact repository. The simplest way to do this is to download https://raw.githubusercontent.com/opendaylight/odlparent/master/settings.xml and place it in your ~/.m2 folder (wherever that is — it depends on your operating system).
Yes, your settings.xml should be updated. An alternative way of updating (though same result as above):
Run this from your terminal:
cp -n ~/.m2/settings.xml{,.orig} ; \wget -q -O - https://raw.githubusercontent.com/opendaylight/odlparent/master/settings.xml > ~/.m2/settings.xml
As suggested by stephen, path may be different based on your OS. Change it accordingly.

Trying to precompile assets on AWS Elastic Beanstalk

2013-11-03 20:30:48,342 [INFO] (30173 MainThread) [directoryHooksExecutor.py-29] [root directoryHooksExecutor info] Output from script: /usr/bin/ruby1.9 /usr/bin/rake assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets
rake aborted!
Command failed with status (): [/usr/bin/ruby1.9 /usr/bin/rake assets:prec...]
Tasks: TOP => assets:precompile
(See full trace by running task with --trace)
Rake task failed to run, skipping asset compilation.
How do I precompile assets on AWS Elastic Beanstalk ?
I am getting following error
Precompilation of assets can be done at deployment time, and to do it, go to the root of your Rails project and create a .ebextensions directory with a .config file in it. You can specify precompilation there. I'm running a Rails app with Elastic Beanstalk and had problems with fonts not being shown. Here's my .ebextensions/ruby.config file:
packages:
yum:
git: []
container_commands:
01_assets:
command: RAILS_ENV=production bundle exec rake assets:precompile
leader_only: true
You can customise the system by running scripts before or after your application deployment.
Basically, you need to create a .ebextensions directory in your source code and insert your commands and customisation steps in a YAML syntax.
The documentation explains the details.
Beware that these commands are run as 'root' with no environment variable setup. If you need variables like PATH or other, it is up to you to position them.
Here is a sample I wrote for an application which required a NodeJS module installation from the source.
packages:
yum:
gcc: []
gcc-c++: []
container_commands:
10_pre_install_sqlite3:
command: "/opt/elasticbeanstalk/node-install/node-v0.10.21-linux-x64/bin/npm install sqlite3#2.1.16 --build-from-source"
cwd: "/tmp/deployment/application"
env:
HOME: "/root"
PATH: "/sbin:/bin:/usr/sbin:/usr/bin:/opt/aws/bin"

Git-svn 'refs/remotes/tags' exists; cannot create

I have a problem when trying to migrate the subversion repository to Git repository
I run by following command
git svn clone -s --ignore-paths="tags" svn://localhost/web .
and I got the error message as below,
branch_from: /branches/tags => /branches/tags/3.7
Found possible branch point: svn://localhost/web/branches/tags/3.7 => svn://localhost/web/tags/3.7, 15131
Initializing parent: refs/remotes/tags/3.7#15131
W: Ignoring error from SVN, path probably does not exist: (160013): Filesystem has no item: File not found: revision 101, path '/branches/tags/3.7'
W: Do not be alarmed at the above message git-svn is just searching aggressively for old history.
This may take a while on large repositories
Found possible branch point: svn://localhost/web/branches/workspace_production_3.0 => svn://localhost/web/branches/tags/3.7, 10538
Found branch parent: (refs/remotes/tags/3.7#15131) a7067c8515c17c7f0bf8c6390a785426a8de5b83
Following parent with do_switch
Successfully followed parent
error: 'refs/remotes/tags' exists; cannot create 'refs/remotes/tags/3.7#15131'
fatal: Cannot lock the ref 'refs/remotes/tags/3.7#15131'.
update-ref -m r10539 refs/remotes/tags/3.7#15131 67f3c547c7dfac657fcfd7759746f44eb74b187f: command returned error: 128
actually I don't want to ignore any path, but seem like tags occurs the problem, so I put it to the ignore-path.
Do I missing something?
For my repository, there are the previous revision that contains non-standard repository form like /branches/tags , so, I fixed by re-create git rep with following command
git svn init -s --ignore-paths="^tags|^branches/tags" svn://localhost/web .
git svn fetch